DZIRCMS

I often use the same entries for client settings. It would be helpful if often used ones could be added via click. Examples:
tinymce|forced_root_block|
articles|show-new-window-checkbox|true
… (Markus Hübner (mchubi))

If you have a categorie filled with many articles - e.g. for a newslist - and you want to delete several articles, you have to do that one by one. It would be quite useful, if there’d be the possibility to select those articles via checkboxes - like it is in filemanagement - and, after confirmation of course ;o) - delete them at one step.
(Markus Hübner (mchubi))

<p>Show thumbnails with transparency</p>

<p>Show all messages and questions (&quot;Are you sure…&quot;) in the backend with style position: fixed; so that they definitely are visible for the user without the need to scroll up first.<br/>(Steffen (derSteffen))</p>

<p>see contenido forum http://forum.contenido.org/viewtopic.php?f=62&amp;t=32660</p>

<p>If you delete a folder using ftp it isn’t deleted in db. For files you have to call the folder in filemanager, but if you also delete the folder that cannot work.<br/>We have to check if we can enhance the checks in filemanager to check for missing folders.</p><p>Also we have to remember that for the new version of filemanager.</p><p>see con forum http://forum.contenido.org/viewtopic.php?f=62&amp;t=32693</p>

<p> • check for usefull plugins</p>

<p>In the file manager, add a button which will show, for the current folder, which of the files are in use.<br/>We will have to check for CMS-Types (like CMS_IMG) as well as article content (over the database?).<br/>This is needed for the ability to delete old, no longer used files.</p><p>In addition, we might also check per file on a delete request, if not already checked through the button.</p>

<p>1)<br/>I quite often use my netbook to update my webcontent. One category contains more than 70 articles and the next is always a copy of the last one which will be altered. So I have to select page 4 first, which is not a problem. But humans are normally lazy - so am I - and I always have to scroll to the bottom to see the page-selector. So it would be great to have that selector not only below, but also above the article-listing. Like it is in filemanagement.</p><p>2)<br/>At the moment you can sort the articles of a category by using the dropdown above the listing. It would be nice if you could do that by clicking on the columns header.</p><p>(Markus Hübner (mchubi))</p>

<p>Rebuild the backend with a new look-and-feel.</p>

<p>Build a new hierarchical structure for class files in /drugcns/classes and arrange the class files into it.</p><p>First thoughts are (please add thoughts):<br/>/drugcms<br/>-&gt; /classes<br/>-&gt; -&gt; /abstract<br/>-&gt; -&gt; -&gt; /html5<br/>-&gt; -&gt; -&gt; /template<br/>-&gt; -&gt; -&gt; -&gt; /parser.php -&gt; class clAbstractTemplateParser()<br/>-&gt; -&gt; /backend<br/>-&gt; -&gt; /common<br/>-&gt; -&gt; -&gt; /content<br/>-&gt; -&gt; -&gt; -&gt; /article.php -&gt; class Article()<br/>-&gt; -&gt; -&gt; -&gt; /template_config.php - class TemplateConfig()<br/>-&gt; -&gt; -&gt; /security<br/>-&gt; -&gt; -&gt; /generic<br/>-&gt; -&gt; -&gt; -&gt; /db.php -&gt; class GenericDB()<br/>-&gt; -&gt; -&gt; /template<br/>-&gt; -&gt; -&gt; -&gt; /counter_function_parser.php -&gt; class clCounterFunctionParser()<br/>-&gt; -&gt; -&gt; -&gt; /if_function_parser.php -&gt; class clIfFunctionParser()<br/>-&gt; -&gt; -&gt; -&gt; /str_api_function_parser.php -&gt; class clAtrApiFunctionParser()<br/>-&gt; -&gt; -&gt; -&gt; /template.php -&gt; class Template()<br/>-&gt; -&gt; /frontend<br/>-&gt; -&gt; -&gt; /output<br/>-&gt; -&gt; -&gt; -&gt; /compressor.php -&gt; class OutputCompressor()<br/>-&gt; -&gt; -&gt; /groups.php -&gt; class<br/>-&gt; -&gt; -&gt; /logic.php -&gt; class<br/>-&gt; -&gt; -&gt; /permissions.php -&gt; class<br/>-&gt; -&gt; -&gt; /users.php -&gt; class</p>

<p>Currently, after clicking the &quot;move tree&quot; button, one can only &quot;drop&quot; it in another category, where it will show up as the last subcategory, and one must move it up until it reaches it&#039;s desired position, which takes some time on large websites.<br/>In future, after clicking the &quot;move tree&quot; button, we will show &quot;drop&quot; buttons before and after each other category, so one can drop the moved tree in the right position right away.</p>

<p>Make it possible to exchange modules in the article&#039;s template configuration.<br/>This makes it much easier for authors to &quot;design&quot; their articles.<br/>But for this, there must be an option with the templates (style -&gt; templates) with each container to lock and/or hide it from the article configuration.</p>

<p>Be sure to add some kind of query checker which makes the queries database independant (for example strip &quot;TYPE=MYISAM&quot;).</p>

<p>Implement a possibility for (sys)admins to hide config areas of certain modules in category and article configuration for certain user groups.<br/>One possibility is to show all modules in a list with checkboxes, where they can be checked to hide them.<br/>Default is to hide for all non-admins, but there should be an option to select user groups.</p>

<p>The textarea from the template configuration should be shown in the category and article configuration.</p>

<p>http://forum.contenido.org/viewtopic.php?p=154761#p154761</p><p>One should be able to move files in the file manager.<br/>Needed functionality for this:<br/>- move the file in the file system<br/>- correct the path in the database table con_upl<br/>Articles using the file through modules aren’t infected, because they only save the id of the entry in con_upl.<br/>Only articles using the file inside the TinyMCE editor will have a problem.<br/>For this case, we should consider correcting those paths too, or showing a warning message on trying to move the file.</p>

<p>Add options to the preview area which change the size of the viewport to emulate mobile devices.<br/>Offer known sizes with device names (iPhone 5, Galaxy Note 3, …) as well as free width and height entry fields.<br/>This makes it easier for authors to see what the page would look like on those devices, which reduces responsive sites with non-responsive contents.</p><p>Suggestion: http://forum.contenido.org/viewtopic.php?f=36&amp;t=34999.</p>

Implement a system updater, which can, by setting, either update the system on mouse click, or completely automatic at a set daytime.
The automatic update functionality must be restricted to either the primary or secondary version number (2.x.x or 2.0.x).

<p>PHPMailer: Upgrade to newest version</p>

<p>Add a system/client/USER option to show category and article names in a prefered language (tooltip).</p><p>Inspired by http://forum.contenido.org/viewtopic.php?f=92&amp;t=35247#p164661.</p>

<p>In article properties, a list of categories exists to enable the user to move the article.<br/>In this list, the categories the user has no rights for are also listet.<br/>Filter them out according to the user&#039;s rights.</p><p>Also rework the function createCategorySelect() for the same filter.<br/>But here we must think of a possibility to remain settings from other users, because they would get lost on saving the configuration.</p>

Implement the possibility to redesign a website without showing changes live or working in a copy of the website.

Thoughts:

• use a new "dummy client" and takeover the changes on button press.
• create a layouts folder and move the design stuff (css, images, js, …) in there in a subfolder per design (we'll have to save the layouts and templates as files then), then create a backend select field to switch the design at will.

Either case, we need a url parameter to switch to an inactive design for testing purposes.

<p>On using TinyMCE, the backend pageneeds to reload on opening and saving.<br/>By showing the editor in a popup (or inline, we already have a small one there) and saving through Ajax (and updating the page content), work gets easier and faster because the need to scroll down again to get to the next working position is minimized.</p>

<p>Restrict attempts to log into the backend to a certain number.<br/>Check the IP address and/or the browser info for this, not the login (the real user might try to login in between).</p>

<p>User Rights: User with set rights should be able to give other (new) users same rights: http://forum.contenido.org/viewtopic.php?f=92&amp;t=36469&amp;view=unread&amp;sid=7c63b5108740416edb6159e211c9d66f#p167847</p>

<p>Add an option to delete contained articles and sub-categories on deleting a category.<br/>Delete, if set, through this tree step by step, first deleting all articles in the deepest category, then deleting that category.<br/>Repeat this way up until the selected category is empty and then delete it, finishing the job.</p>

<p>As for the internationalization, drugCMS needs to support more languages (setup, backend, plugins, …).</p>

<p>Recode the login form and code to get the session key ($contenido) after the login process.<br/>As for now, the session key ist in the login form, which makes it impossible to login through an automated script.</p>

<p>Create a folder named &quot;system&quot; in which the system files and folders get moved.<br/>Only the client folder(s) remain in root.<br/>The new folder must be renamed on setup, so only the sysadmin knows it&#039;s name.<br/>In this folder, there must be a .htaccess which routes to the /&lt;new folder&gt;/drugcms/ folder.<br/>The drugCMS backend then is reachable only by entering this folder&#039;s name after the domain.<br/>CAUTION: The client&#039;s config.php file needs to be altered as well!</p><p>As the setup folder get&#039;s moved into this new folder too, setup has to change it&#039;s address on the renaming process in order to continue.</p><p>On (cross-)upgrading from drugCMS 2.0.x/Contenido 4.6.x and 4.8.x, we have to remove the old system folders and files, as they are not within this new folder.<br/>And in this situation the sysadmin (who does the upgrade) also has to enter a new name for this folder, except if he removed it and moved the contained system files and folders back to root (he might already work with a subdomain for the backend).</p>