RhodeCode - issues: Issueshttps://issues.rhodecode.com/https://issues.rhodecode.com/favicon.ico?16960560042022-07-06T07:19:07ZRhodeCode - issues
Redmine Documentation - Support #5683 (New): Schemas (Structured Data) Snippetshttps://issues.rhodecode.com/issues/56832022-07-06T07:19:07ZToday Deals
<a name="Schemas"></a>
<h1 >Schemas<a href="#Schemas" class="wiki-anchor">¶</a></h1>
<p>Schema.org is a collaborative, community activity with a mission to create, maintain, and promote schemas for structured data on the Internet, on web pages, in email messages, and beyond.<br>
Founded by Google, Microsoft, Yahoo and Yandex, Schema.org vocabularies are developed by an open community process, using the <a href="mailto:public-schemaorg@w3.org">public-schemaorg@w3.org</a> mailing list and through GitHub.</p>
<a name="Demo"></a>
<h1 >Demo<a href="#Demo" class="wiki-anchor">¶</a></h1>
<p>Page demo: <a href="https://www.todaydeals.org/store/udemy" class="external">https://www.todaydeals.org/store/udemy</a> <br>
Created by the team building <a href="https://www.todaydeals.org" class="external">https://www.todaydeals.org</a> </p>
<a name="Technical-guidelines"></a>
<h1 >Technical guidelines<a href="#Technical-guidelines" class="wiki-anchor">¶</a></h1>
<p>You can test compliance with technical guidelines using the Rich Results Test and the URL Inspection tool, which catch most technical errors.<br>
Format<br>
In order to be eligible for rich results, mark up your site's pages using one of three supported formats:<br>
<br>
JSON-LD (recommended)<br>
Microdata<br>
RDFa</p>
RhodeCode CE/EE - Bug #5612 (New): CPU cores getting maxed out by VCSServer on Repository Size re...https://issues.rhodecode.com/issues/56122020-04-08T18:57:58ZRenaud Lepage
<p>Please note that this happens on a RhodeCode CE instance, running the latest RhodeCode code, but running on a Virtual Private Server machine with fairly "restricted" specs (one virtual CPU, 2gb RAM). Weak by any metrics.</p>
<p>Condition: Using a freshly imported SVN repository that's not indexed or anything</p>
<p>Hitting "Show Repository Size" starts some kind of "runaway process", or possibly a "go through each commit in historical order", from the RhodeCode "Main Service" (community-1) to the VCS Server. This makes the two VCSServer workers max out the one virtual CPU my VPS instance has for some reason - likely because VCSServer does some big processing on each commit to get the size, but I can't be sure.</p>
<p>Setting prio to Low because I'm not a paying client.</p>
Documentation - Bug #5598 (New): Typo in force delete commandhttps://issues.rhodecode.com/issues/55982020-03-19T20:10:07ZJoseph Sible
<p>Running the command at the bottom of <a href="https://docs.rhodecode.com/RhodeCode-Enterprise/admin/repo_admin/repo-admin-tasks.html" class="external">https://docs.rhodecode.com/RhodeCode-Enterprise/admin/repo_admin/repo-admin-tasks.html</a> will fail with the message "No matching instances found to run the iShell." The problem is that it contains a typo: it uses "Enterprise-1" with an uppercase E instead of "enterprise-1" with a lowercase e.</p>
RhodeCode CE/EE - Bug #5558 (Resolved): Commit compare window covers texthttps://issues.rhodecode.com/issues/55582019-07-07T21:53:10ZCatalin Salgau
<p>Commit compare window covers text<br>
Seen on pre-pull-request commit or when hitting "compare origin on a fork repository" (and reaching this url, for example)<br>
<a href="https://code.rhodecode.com/rhodecode-enterprise-ce/compare/rev%40tip...rev%40tip?merge=1" class="external">https://code.rhodecode.com/rhodecode-enterprise-ce/compare/rev%40tip...rev%40tip?merge=1</a></p>
RhodeCode CE/EE - Feature #5536 (Resolved): Ability to disable server-side SSH key generationhttps://issues.rhodecode.com/issues/55362019-02-11T19:42:50ZCatalin Salgau
<p>Generating a private/public SSH key pair may be user-friendly, but shipping this from the server can pose security concerns.<br>
Please add a way to disable key generation and/or provide client client-side key generation(Web Crypto APIs are available in most modern browsers)<br>
Thanks</p>
Documentation - Bug #5439 (New): JIRA Integration description: Wrong sample linkhttps://issues.rhodecode.com/issues/54392018-02-14T14:25:34ZMalte Onnen
<p>The sample link described <a href="https://docs.rhodecode.com/RhodeCode-Enterprise/issue-trackers/issue-trackers.html#jira-integration" class="external">here</a> should rather be <br>
<a href="https://myissueserver.com/browse/${id}" class="external">https://myissueserver.com/browse/${id}</a><br>
than<br>
<a href="https://myissueserver.com/issue/${id}" class="external">https://myissueserver.com/issue/${id}</a></p>
Documentation - Task #5408 (Resolved): Upate nginx documentation for non standard SSL porthttps://issues.rhodecode.com/issues/54082017-12-02T16:04:42ZMaurice Müller
<p>I'm currently in an evaluation process for rhodecode. During my test setup it give me a headache that the given nginx example was not working fully in my set up (login and logout were getting a timeout although the user was logged in / out).</p>
<p>After a long search I figured out that the non standard SSL port was the issue. This can easily be fixed by replacng the following in the proxy.conf file (<a href="https://docs.rhodecode.com/RhodeCode-Enterprise/admin/nginx-tuning.html" class="external">https://docs.rhodecode.com/RhodeCode-Enterprise/admin/nginx-tuning.html</a>) :</p>
<p>replace:<br>
proxy_set_header Host $host;<br>
with:<br>
proxy_set_header Host $host:$server_port;</p>
<p>I hope this helps some other guys in the future ;)</p>
RhodeCode Appenlight - Bug #5342 (New): Broken link [Applications Modify application]https://issues.rhodecode.com/issues/53422017-06-21T21:21:50ZBartłomiej Wołyńczyk
<p>Description:<br>
Link in applications setting is leading to main application page instead documentation.</p>
<p>"How to connect your application?<br>
Visit our developer documentation for step-by-step integration instructions."<br>
developer documentation ->> <a href="https://appenlight.rhodecode.com/" class="external">https://appenlight.rhodecode.com/</a><br>
instead ->> <a href="https://getappenlight.com/page/api/main.html" class="external">https://getappenlight.com/page/api/main.html</a> ??</p>
<p>Steps to reproduce:</p>
<ol>
<li>Go to Applications </li>
<li>Chosen Application -> Update</li>
<li>On Right Top there is link leading to developer documentation. </li>
</ol>
RhodeCode CE/EE - Task #4289 (New): [ce, ee] clean up pygments lexer functions + handlinghttps://issues.rhodecode.com/issues/42892016-10-21T14:40:28ZDaniel Ddaniel@rhodecode.com
<p>Currently there are a few lexer functions that seem duplicated/incoherent with each other. This seems to be also tied with the rc extensions which can define custom lexers/file extension mappings in example-ext.py:</p>
<pre><code>
# =============================================================================
# END OF UTILITY FUNCTIONS HERE
# =============================================================================
# Additional mappings that are not present in the pygments lexers
# used for building stats
# format is {'ext':['Names']} eg. {'py':['Python']} note: there can be
# more than one name for extension
# NOTE: that this will override any mappings in LANGUAGES_EXTENSIONS_MAP
# build by pygments
EXTRA_MAPPINGS = {}
# additional lexer definitions for custom files it's overrides pygments lexers,
# and uses defined name of lexer to colorize the files. Format is {'ext':
# 'lexer_name'} List of lexers can be printed running:
# >> python -c "import pprint;from pygments import lexers;
# pprint.pprint([(x[0], x[1]) for x in lexers.get_all_lexers()]);"
EXTRA_LEXERS = {}
</code></pre>
<p>Then there are the functions get_custom_lexer and the FileNode attributes <code>filenode.lexer</code> which don't seem to follow the same logic - the filenode lexer for example seems to prefer a lexer matching the filename instead of a defined custom lexer.</p>
<p>We should use a common base for getting a lexer - one that first returns custom lexer mappings (so that for example .html can be mapped to mako).</p>
<p>Extending on this it could be possible to make the file extension => lexer mapping a per repository setting, exposed via the ui, which would give the best usability in terms of letting each repo specify which lexer to prefer ... again for example <code>.html => mako</code> </p>
RhodeCode CE/EE - Task #4259 (Resolved): Events, create post-create-user eventhttps://issues.rhodecode.com/issues/42592016-10-03T20:51:03ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>I think it'd be usefull to create post-create user event, and add it to webhook/slack/hipchat.</p>
<p>Use case is to create accounts in external systems via webook / notify via chat applications about new users.</p>
RhodeCode Appenlight - Feature #4220 (New): Search params allow sorting of result.https://issues.rhodecode.com/issues/42202016-09-06T16:33:29ZTomek Banasiak
<p>Hi,</p>
<p>Ability for sorting asc, desc by search result for example by avg duration, location etc would be cool.</p>
RhodeCode CE/EE - Bug #4155 (Resolved): Date of Last Change is not displayed correctlyhttps://issues.rhodecode.com/issues/41552016-08-07T11:17:09ZDmitry Konchalenkov [staff]dmitry@rhodecode.com
<p>Expected: <em>Last Change</em> should be the date of the latest commit. See screenshot.<br>
Actual: </p>
<ul>
<li>either <em>Last Change</em> doesn't use the date of the latest commit</li>
<li>or <em>Last Change</em> uses the time zone incorrectly</li>
</ul>
RhodeCode CE/EE - Bug #4154 (New): [ce, ee] user register via github captchahttps://issues.rhodecode.com/issues/41542016-08-05T22:51:47ZDaniel Ddaniel@rhodecode.com
<p>Found on code.rhodecode.com - sign up using github account - captcha is asked but not verified.</p>
RhodeCode CE/EE - Bug #4040 (New): [ce, ee] logout when logged out causes 403 Cross-site request ...https://issues.rhodecode.com/issues/40402016-06-22T21:09:03ZDaniel Ddaniel@rhodecode.com
<p>Reproduce:</p>
<ul>
<li>Login to rhodecode</li>
<li>Logout in another tab</li>
<li>Click logout in original tab</li>
</ul>
RhodeCode Appenlight - Feature #4017 (New): application logos need helphttps://issues.rhodecode.com/issues/40172016-06-14T11:52:12ZLisa Quatmannlisa@rhodecode.com
<p>see attached</p>
<p>surely we can make this prettier</p>