CMSimple_XH–Forum

Hi everybody!

Time to gather items for sprint #5.

1. Prefix special page names with "xh" Don't import arbitrary globals from the query string
2. Login Form detached from Template
3. Introduce xhsuccess for general success messages after redirection (withdrawn?)
4. SystemCheck to state present state
5. add breadcrumb markup for locator
6. filebrowser: attempt to delete a unempty directory
7. Move editorhooks to respective plugin
8. Add check for "secure" password Fix password autocomplete issues in config
9. add rel=nofollow to loginlink() and printlink()
10. Replace TinyMCE 3 as default editor
11. Change page splitting to new XH-split way
12. tinyMCE: Toolbar Configuration in Back-End
13. More memory efficient handling of content
14. Cater to Filenames with non ASCII Characters
15. Reliable setting of $s
16. stricter distinction between $_GET and $_POST
17. Filebrowser: customizable filters for individual folders
18. Submit GET forms to the plugin adminstration
19. Multiple sites sharing userfiles/
20. Filebrowser: resize large images on upload
21. optional usage information
22. Remove support for #CMSimple hide|remove#

Please make suggestions about which items from the roadmap to include in sprint #5.

Ok, so here are mine, just a few minor topics to clean-up the roadmap with this sprint:

• Login Form detached from Template
  
• Introduce xhsuccess for general success messages after redirection (seems we can close that topic WRT XH_message() ??)
  
• SystemCheck to state present state
  
• add breadcrumb markup for locator (seems we forgot in sprint#4 ?)

And BTW, we should have a look at this topic, since named sessions are already included.

Thanks, Holger. I've updated the list.

I suggest to continue discussion (if necessary) in the respective threads, but a remark regarding "add breadcrumb markup for locator": this had not been forgotten, but rather I was not sure about the details, and there was no further discussion, so I only did the basic refactoring, what should make it quite easy to add the desired markup (whatever we'll choose).

Holger wrote:And BTW, we should have a look at this topic, since named sessions are already included.

Indeed. That would appear to make most explicit rules obsolete, and the rest (e.g. use a reasonable prefix for the session variables) are pretty much uncontroversial, so there's no need for further discussion. I shall add the condensed info to the XH wiki.

I've updated the links in the OP to point to the respective Github issues. Also I've changed item (1) to a related issue, which should probably be resolved (or not) before the originally planned issue is going to be tackled.

I've replaced (8) with a related issue, which should better be solved first, because otherwise we'd had to consider checking whether the password is "secure" also on the client-side.

I have just suggested a timeline for CMSimple_XH 1.7.0, and to be able to manage it ever, I've considerably extended the list of items for this sprint.

I've marked all 22 issues on Github with the label "voting", so you can easily find them.

Note that there are pull requests for all features which I consider reasonable to implement for XH 1.7.0, except for the filebrowser bug which has already been fixed (complain, if you don't like this fix), and the new page splitting, which is in a separate code repository. This clarifies what to vote upon, and you can actually try it out. Please preferably vote by adding your reaction where it is not misunderstandable (e.g. add +1/-1 to my comment where I suggested to postpone a feature), or by adding a short comment (longer discussions might better done in the respective forum thread). Those who don't have a Github account can sign up for one, or if necessary vote by replying to the forum discussion thread (I'll try to forward this to the respective Github issue).

Voting ends in 18 days, i.e. on March, 15th.

Happy voting!

cmb wrote:Voting ends in 18 days, i.e. on March, 15th.

Ping.

Voting has ended. Thanks to all participants!

I've changed the labels and milestones, respectively, according to the voting results. I'm going to implement all enhancements that have been marked "to be implemented" ASAP.

cmb wrote:I'm going to implement all enhancements that have been marked "to be implemented" ASAP.

Done!