Changelog for themes - My-Little-Forum/mylittleforum GitHub Wiki

• the template main.tpl got an additional link to top of the page in the right footer menu; additionally the two RSS-links was separated into two list items (line 82 and following)
• in correlation with that a few changes occured in the CSS code (style.css: lines 84 (removed padding) and 109 (added selector #footermenu li a.rss), same but minified rules in style.min.css: lines 60 and 76)
• the subtemplates entry.inc.tpl (in line 50), thread.inc.tpl (in line 68) and thread_linear.inc.tpl (also in line 68) got an additional link to top of the page in the options menu (bookmark handling, editing or deleting the entry and so on) located usually below the entry; see therrefore also the addition of the rule for #footermenu a.go-to-top-link in style.css (lines 111 and 112) and in style_min.css (line 77)
• because of the added backup functions for subscriptions and tags two new links was added in the link list of the backup page in the admin area (code line 878, links for backup modes 11 and 12 at the end of the line)

• Because of the added checks for the CSRF-token for the calls to delete one or more postings, a few templates (entry.inc.tpl, index.inc.tpl, index_table.inc.tpl, thread.inc.tpl, thread_linear.inc.tpl) was changed to add the token to the calls. Please search for {$CSRF_TOKEN} in the view of changed places to locate the exact places you have to change in your own theme. You will not be able to delete a posting without adapt these changes!

• To ensure the correct height of an image in the Ajax-preview the height is set to auto in the CSS files.
• The settings section in the admin.inc.tpl got a new variable name. Previous variable $settings is now named $edSet. See the details in the file tab of pull request 449.

• The CSS of the default theme got one update to prevent the thumbnail images in a posting to take the full height of the posting. The relevant changes are accessible in pull request #442.

• The user_edit.inc.tpl got a new table row with a link to a close-account-function. The function itself causes a new template named user_remove_account.inc.tpl.
• We forgot to remove a password confirmation field from the change-password-function in the template user_edit_pw.inc.tpl.
• We removed a pair of classes from several form fields in the admin panel. Changes apply to the template admin.inc.tpl.
• The addition of two links for resetting the acceptance to the terms of use and/or the data privacy statement applies also to the admin.inc.tpl.
• To list the possible new requirements for the password strength, changes to the templates register.inc.tpl and user_edit_pw.inc.tpl are necessary.

No new changes in the default theme.

• Several forms in the admin template got hidden fields for CSRF-tokens. This is to prevent attacks from other browser tabs. The form fields are mandatory. The values from forms will not be processed without the CSRF-token fields.
• Because of the new possibility to make the password input visible in the registration form, the second password field for the confirmation of the password was removed and the following form fields got new, lower tab indexes.
• To show a message about an processed unsubscription from a forum entry we introduced a new subtemplate named posting_unsubscribe.inc.tpl.

• The names of several form fields in the registration and the posting form are built dynamically from now on. Because of that the name attributes of these fields are variables in the templates. Additionally a few fields of the registration form changed their order to prevent an issue with the Firefox browser (the password fields follows now immediately after the user name field). See therefore …
  • … the related changes in posting.inc.tpl
  • … the related changes in register.inc.tpl

• The new template user_agreement.inc.tpl contained an error in the allocation of the variable for the URL of the terms of use agreement. Instead the correct URL the one for a data privacy statement got included. If there was no URL for a privacy statement, the user saw a blank page in the iframe when the user had to agree to a terms of use agreement.
• There was an orphan underscore in line 85 of the file admin.inc.tpl. It's very unlikely, that one copied this char to an own theme but for the sake of completeness …

• added a new template for the output of an external document (currently the data privacy statement or the terms of use) named subtemplates/user_agreement.inc.tpl
• added a rule for setting the height of the iframe in the new template in the files style.css (line 167) and style.min.css (line 119)
• changed the order of elements in the HTML-header in main.tpl the meta element for the charset and the title element interchanged their order
• added the section for the data privacy statement in the settings view in subtemplates/admin.inc.tpl (lines 80 to 83)
• several changes because of the data privacy statement code in the posting form in subtemplates/posting.inc.tpl
  • added a hidden input in the lines 73-75
  • added the variable $data_privacy_agreement to the if-condition in line 235
  • added the necessary form elements for agreeing to the data privacy statement in lines 261-266
  • reset the values of the attribute tabindex for the form elements that follows the new block in the lines 278 and 284
• several changes because of the data privacy statement code in the registration form in subtemplates/register.inc.tpl
  • added the necessary form elements for agreeing to the data privacy statement in the lines 41-44
  • reset the values of the attribute tabindex for the form elements that follows the new block in the lines 50, 53 and 56

Mouse cursor pointer is added to hovered label elements.

label { cursor:pointer; }

• added hidden input fields for CSRF-tokens to the templates user_edit.inc.tpl, user_edit_email.inc.tpl and user_edit_pw.inc.tpl.

For spam protection, new text fields are added to the forms that should be invisible.

• new hidden field for CSRF-token in posting.inc.tpl
• new fields for honeypots in posting.inc.tpl, made invisible with the new CSS rule for form p.hp
• new fields for honeypots in register.inc.tpl, made invisible with the new CSS rule for form p.hp
• tabindices for all form fields in register.inc.tpl
• form p.hp { display: none; } new introduced rule block

A shortened example for a list item before the change …

<li><a href="index.php?id=#1"><span class="read">Subject line</span><br />date of the entry</a></li>

… and after the change.

<li><a href="index.php?id=#1" class="read"><span class="entry-title">Subject line</span><br /><span class="entry-date">date of the entry</span></a></li>

Additionally the blocks of the bottombar of the table view in index_table.inc.tpl got the same structure of Ids and classes as the structure in the sidebar of the thread view exists. This changes caused on their part changes in the CSS-files.

• #sidebar, new: width: 13em
• #latest-postings, removed: width: 13em, changed: margin: 0 0 20px 20px => margin: 0 0 20px 0
• #tagcloud, removed: width: 13em, changed: margin: 0 0 20px 20px => margin: 0 0 20px 0
• #modmenu, removed: width: 13em, changed: margin: 0 0 20px 20px => margin: 0 0 20px 0
• #latest-postings ul, new: max-width: 100%
• #latest-postings li a, removed: font-size:0.82em, new: background-color: #f0f0f0, changed: padding:3px 5px 3px 5px => padding:3px 5px
• #latest-postings li a:visited, #latest-postings li a.read, new introduced rule block
• #latest-postings li a:visited .entry-title, #latest-postings li a.read .entry-title, new introduced rule block
• #latest-postings li a:hover, enhanced to #latest-postings li a:focus, #latest-postings li a:hover
• #latest-postings li a:focus .entry-title,#latest-postings li a:hover .entry-title, new introduced rule block
• #latest-postings li a .entry-date,#latest-postings li a.read .entry-date, new introduced rule block
• #latest-postings li a span, removed rule block

The author of #267 is Romchik

• themes\default\main.tpl, bug fix for meta elements
• includes/index.inc.tpl, deduplicated title-attribute
• includes/index_table.inc.tpl, deduplicated title-attribute

• #bottombar:not(.js-display-fold) h3.sidebar, new introduced rule block
• #bottombar p.tagcloud, removed rule block
• #bottombar p.tagcloud strong, removed rule block
• #bottombar #tagcloud p, new introduced rule block, replacement for #bottombar p.tagcloud and #bottombar p.tagcloud strong
• #bottombar .latestposts, removed rule block
• #bottombar .latestposts li, removed rule block
• #bottombar .latestposts a, removed rule block