Projects: Issueshttp://projects.andriylesyuk.com/http://projects.andriylesyuk.com/plugin_assets/andriy_lesyuk/images/s-andy.ico2018-05-17T09:56:37ZProjects
Redmine Contact Form - Feature #2442 (New): Put sender's email into Fromhttp://projects.andriylesyuk.com/issues/24422018-05-17T09:56:37ZAndriy Lesyuks-andy@andriylesyuk.com
<p>Right now, the plugin puts sender’s email into the Reply-To header and the From header uses the Redmine’s emission email address. As a result, when I click Reply some email clients (such as Thunderbird) do not fill the To address of the replying email (so I need to do this manually each time).</p>
<p>So, I wonder, if the plugin should user the From header instead?</p> WordMine - Feature #2433 (Open): Link Redmine issue with WordPress commenthttp://projects.andriylesyuk.com/issues/24332017-12-09T18:05:10ZAndriy Lesyuks-andy@andriylesyuk.com
<p>Some users report issues in WordPress comments, so it would be great, if the plugin allowed to quickly import them into Redmine as issues. For this a new action link can be added, e.g., “Create issue”.</p>
<p>It would also be great to be able to link comments to (existing) Redmine issues (without importing them as new ones). Such comments can, probably, be added to issues as notes. Certainly, such notes should include links to blog comments too.</p> ISSUE-id - Bug #ISSUE-14 (Open): Escaping #ISSUE-id Textile rule does not workhttp://projects.andriylesyuk.com/issues/ISSUE-142017-12-02T21:46:29ZAndriy Lesyuks-andy@andriylesyuk.com
<p>Escaping ISSUE-id’s special Textile syntax rule does not work, if multiple IDs are specified in one line. For example:</p>
<pre>
!#ISSUE-1, !#ISSUE-2 and !#ISSUE-3
</pre>
<p>Demo: <img src="#ISSUE-1," alt="" /><a class="issue tracker-9 status-5 priority-5 priority-default closed" title="Bulgarian translation (Closed)" href="http://projects.andriylesyuk.com/issues/ISSUE-2">#ISSUE-2</a> and #ISSUE-3</p>
<p>This happens because Redmine treats <code>!#ISSUE-1, !</code> as an image. Therefore, <code>parse_redmine_links_with_issue_id</code> gets the following <code>text</code>:</p>
<pre>
Demo: <img src="#ISSUE-1," alt="" />#ISSUE-2 and !#ISSUE-3
</pre>
<p>The same applies to legacy IDs:</p>
<p>Demo: <img src="#1," alt="" /><a class="issue tracker-2 status-5 priority-5 priority-default closed" title="User needs some way to see available activities (Closed)" href="http://projects.andriylesyuk.com/issues/2">#2</a> and <a class="issue tracker-7 status-5 priority-4 priority-low2 closed" title="Create more bug related contexts (Closed)" href="http://projects.andriylesyuk.com/issues/3">#3</a></p>
<p>So, it’s not a problem in the plugin, but in the Redmine core.</p> Red-Andy - Feature #2414 (Incomplete): Break long application.css into sections?http://projects.andriylesyuk.com/issues/24142016-10-10T21:14:18ZAndriy Lesyuks-andy@andriylesyuk.com
<p>The CSS code is not readable. It’s hard to find rules, when needed.</p>
<p>It should be reordered at least. Probably, some parts can be moved to separate files.</p> WikiNG - Feature #2413 (Incomplete): Custom links syntaxhttp://projects.andriylesyuk.com/issues/24132016-10-06T07:09:28ZAndriy Lesyuks-andy@andriylesyuk.com
<p>Currently, the plugin supports external links using the syntax like <code>[[redmine>#9638]]</code> (this one generates a link to the corresponding <a href="http://www.redmine.org" class="external">Redmine</a> issue)...</p>
<p>I also think about adding support for, e.g., <code>[[debian>#9638]]</code>... The problem is that not every customer will need to have links to Debian issues.</p>
<p>A good alternative is to support custom links, syntax of which can be configured. Thus, the plugin can come with a form like:</p>
<p><img src="http://projects.andriylesyuk.com/attachments/download/657/custom-links.png" class="wiki-class-wiking wiki-class-shadow" alt="" /></p>
<p>This way every customer will be able to add as many custom issues links as he needs.</p>
<p>This issue conflicts with <a class="issue tracker-7 status-8 priority-4 priority-low2" title="External Redmine links (Incomplete)" href="http://projects.andriylesyuk.com/issues/1906">#1906</a>.</p> Projects - Feature #2406 (Open): List of forks for projectshttp://projects.andriylesyuk.com/issues/24062016-08-29T11:13:17ZAndriy Lesyuks-andy@andriylesyuk.com
<p>Many projects now have forks. Some of them just contain fixes <em>(due to my inactivity)</em> and others come with new features. It would be great to list all such known forks in projects, e.g., in a block on sidebar. Check <a href="http://projects.andriylesyuk.com/projects/issue-id/repository" class="external">this page</a> for a sample.</p> Sidebar Content - Feature #2405 (Open): Edit link for Wiki pageshttp://projects.andriylesyuk.com/issues/24052016-08-29T11:07:46ZAndriy Lesyuks-andy@andriylesyuk.com
<p>Quick “Edit” link for the Wiki page, that is shown on the sidebar, would be very helpful:</p>
<p><img src="http://projects.andriylesyuk.com/attachments/download/654/Edit.png" alt="" /></p> RedWord - Bug #2368 (Open): Next and prev links for multi-page articleshttp://projects.andriylesyuk.com/issues/23682015-04-02T17:27:19ZAndriy Lesyuks-andy@andriylesyuk.com
<p>Accordingly to Google <code>rel="prev"</code> and <code>rel="next"</code> links of the multi-page article should point to the previous and next pages of the article:<br /><a class="external" href="https://support.google.com/webmasters/answer/1663744">https://support.google.com/webmasters/answer/1663744</a></p>
<p>However, WordPress seems to use “neighbor” articles for these links, what can potentially cause issues.</p> Extended Fields - Feature #2186 (Open): Custom DateTime Fieldhttp://projects.andriylesyuk.com/issues/21862013-04-22T11:47:42ZDileep Kumar Amancharla
<p>Hi,</p>
<p>Would it be possible to make a custome datetime field. If so how it can be done. Please kindly advise.</p>
<p>Thanks in Advance</p> Contact Form - Feature #2170 (Open): Optional email format validationhttp://projects.andriylesyuk.com/issues/21702013-03-10T17:54:22ZRomain Schmitz
<p>By reading some more code I’ve just seen another thing that could be optimized. In the email model you’re checking the address format. There are good reasons to give the user the freedom to disable the format validation. The rfc of email addresses with all its errata documents makes it slightly difficult to pass every valid email address.</p>
<p>Depending on where your plugin is used, it must be guaranteed that every valid email is accepted.</p>
<p>There are good replies in the stackoverflow thread <a href="http://stackoverflow.com/questions/201323/using-a-regular-expression-to-validate-an-email-address" class="external">Using a regular expression to validate an email address</a>.</p> WikiNG - Feature #2076 (Open): HTML Color previewhttp://projects.andriylesyuk.com/issues/20762012-06-28T12:30:35ZAndriy Lesyuks-andy@andriylesyuk.com
<p>If WikiNG meets HTML color code like #C07600 it can make an inline preview by rendering a little box before the color code...</p> Extended Fields - Feature #1881 (Open): Support wiki toolbar for "Default value"http://projects.andriylesyuk.com/issues/18812011-10-26T20:39:05ZAndriy Lesyuks-andy@andriylesyuk.com
<p>Right now it seems to be very complicated and is not critical... So “postponing”.</p> Projects - Feature #1837 (Open): Andriy is now working on...http://projects.andriylesyuk.com/issues/18372011-08-31T17:03:21ZAndriy Lesyuks-andy@andriylesyuk.com
<p>Just an idea:</p>
<p>I usually work on one of the projects... So on the website somewhere can be a status e.g. “Andriy is now working on <ins>Download</ins>” (where <ins>Download</ins> is a link). On the other hand if I don’t work on any of the projects (e.g. freelancing) - “Andriy is now working on his other projects...” <span class="wiking smiley smiley-smiley" title=":)"></span></p>
<p>The status should be triggered manually (using e.g. <a href="/projects/orangutan">Orangutan</a>).</p> Projects - Feature #1804 (Incomplete): Arrows (or similar solution) for project menuhttp://projects.andriylesyuk.com/issues/18042011-07-14T03:26:05ZTim Lin
<p>See attached picture.</p> SCM Creator (+Github) - Feature #1757 (Incomplete): Allow subdirectorieshttp://projects.andriylesyuk.com/issues/17572011-05-30T09:47:58ZJean-Sébastien Bourjsb@zenexity.com