🌍
English
This shows you the differences between two versions of the page.
dev:changes_in_2.5 [2013/01/30 11:18] mistic100 |
— (current) | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Technical changes in Piwigo 2.5 ====== | ||
- | ===== Albums pagination ===== | ||
- | http://piwigo.org/bugs/view.php?id=2614 | ||
- | for theme creators. | ||
- | |||
- | On //index.tpl//, add | ||
- | <code> | ||
- | {if !empty($cats_navbar)} | ||
- | {assign var=navbar value=$cats_navbar} | ||
- | {include file='navigation_bar.tpl'|@get_extent:'navbar'} | ||
- | {/if} | ||
- | </code> | ||
- | right after **{$CATEGORIES}** | ||
- | |||
- | And modify existing photos navbar by | ||
- | <code> | ||
- | {if !empty($thumb_navbar)} | ||
- | {assign var=navbar value=$thumb_navbar} | ||
- | {include file='navigation_bar.tpl'|@get_extent:'navbar'} | ||
- | {/if} | ||
- | </code> | ||
- | |||
- | ===== Add action buttons ===== | ||
- | http://piwigo.org/bugs/view.php?id=2781 | ||
- | for plugin creators. | ||
- | |||
- | Introduction of two template methods to add buttons to index and picture toolbars, allowing you to place buttons relative to each other : | ||
- | <code php> | ||
- | $template->add_picture_button($content, $rank); | ||
- | $template->add_index_button($content, $rank); | ||
- | </code> | ||
- | |||
- | No changes for themes. | ||
- | |||
- | ===== Info./Error messages moved ===== | ||
- | On //index.tpl//, **{include file='infos_errors.tpl'}** was moved away from the main **#content** block.\\ | ||
- | See http://piwigo.org/dev/changeset/18712 | ||
- | |||
- | ===== Jquery UI 1.9 ===== | ||
- | Jquery ui effects filename has changed. For example change | ||
- | <file>footer|combine_script require='jquery.effects.blind'</file> | ||
- | to | ||
- | <file>footer|combine_script require='jquery.ui.effect-blind'</file> | ||
- | We'll have backward naming compatibility for 2.5 version only! | ||
- | |||
- | ===== Password hash ===== | ||
- | |||
- | Until version 2.4 we had a configuration parameter $conf['pass_convert'], which by default was: | ||
- | |||
- | <code php>$conf['pass_convert'] = create_function('$s', 'return md5($s);');</code> | ||
- | |||
- | Now we have 2 configuration settings : | ||
- | |||
- | <code php>// password_hash: function hash the clear user password to store it in the | ||
- | // database. The function takes only one parameter: the clear password. | ||
- | $conf['password_hash'] = 'pwg_password_hash'; | ||
- | |||
- | // password_verify: function that checks the password against its hash. The | ||
- | // function takes 2 mandatory parameter : clear password, hashed password + | ||
- | // an optional parameter user_id. The user_id is used to update the password | ||
- | // with the new hash introduced in Piwigo 2.5. See function | ||
- | // pwg_password_verify in include/functions_user.inc.php | ||
- | $conf['password_verify'] = 'pwg_password_verify';</code> | ||
- | |||
- | They are used this way: | ||
- | |||
- | <code php>if ($conf['password_verify']($clear_password, $row['password'], $row['id']))</code> | ||
- | |||
- | and | ||
- | |||
- | <code php> single_update( | ||
- | USERS_TABLE, | ||
- | array($conf['user_fields']['password'] => $conf['password_hash']($_POST['use_new_pwd'])), | ||
- | array($conf['user_fields']['id'] => $user_id) | ||
- | );</code> | ||
- | |||
- | ===== Website and email on comment form ===== | ||
- | http://piwigo.org/dev/changeset/17351#file6\\ | ||
- | http://piwigo.org/dev/changeset/18164#file12 | ||
- | |||
- | On //comment_list.tpl// we display the website and the email of the author : | ||
- | <code html> | ||
- | <span class="commentAuthor">{if $comment.WEBSITE_URL}<a href="{$comment.WEBSITE_URL}" class="external" target="_blank">{$comment.AUTHOR}</a>{else}{$comment.AUTHOR}{/if}</span> | ||
- | {if $comment.EMAIL}- <a href="mailto:{$comment.EMAIL}">{$comment.EMAIL}</a>{/if} | ||
- | </code> | ||
- | |||
- | On //picture.tpl// we display website url and email inputs : | ||
- | <code html> | ||
- | {if $comment_add.SHOW_EMAIL} | ||
- | <p><label for="email">{'Email'|@translate}{if $comment_add.EMAIL_MANDATORY} ({'mandatory'|@translate}){/if} :</label></p> | ||
- | <p><input type="text" name="email" id="email" value="{$comment_add.EMAIL}"></p> | ||
- | {/if} | ||
- | <p><label for="website_url">{'Website'|@translate} :</label></p> | ||
- | <p><input type="text" name="website_url" id="website_url" value="{$comment_add.WEBSITE_URL}"></p> | ||
- | </code> | ||
- | |||
- | ===== index.tpl, Quick search results albums/tags list ===== | ||
- | |||
- | In index.tpl, inline CSS was replaced with CSS classes .tag_search_results and .category_search_results and CSS rules were moved to themes/default/theme.css: | ||
- | |||
- | <code html>{if !empty($category_search_results)} | ||
- | <div style="font-size:16px;margin:10px 16px"> | ||
- | |||
- | [...] | ||
- | |||
- | {if !empty($tag_search_results)} | ||
- | <div style="font-size:16px;margin:10px 16px"></code> | ||
- | |||
- | were replaced by | ||
- | |||
- | <code html>{if !empty($category_search_results)} | ||
- | <div class="category_search_results"> | ||
- | |||
- | [...] | ||
- | |||
- | {if !empty($tag_search_results)} | ||
- | <div class="tag_search_results"></code> | ||
- | |||
- | Change the code accordingly in your specific index.tpl if any. | ||
- | |||
- | ===== New config var ===== | ||
- | |||
- | The number of maximum Ajax requests at once, for thumbnails on-the-fly generation | ||
- | <code> | ||
- | $conf['maxRequests']=3; | ||
- | </code> | ||
- | |||
- | The categories on PEM (plugins repository) are configurable : | ||
- | <code> | ||
- | $conf['pem_plugins_category'] = 12; | ||
- | $conf['pem_themes_category'] = 10; | ||
- | $conf['pem_languages_category'] = 8; | ||
- | </code> | ||
- | |||
- | ===== MySQLi ===== | ||
- | We introduce MySQLi support in Piwigo 2.5, replacing MySQL. The only main change is that ''pwg_db_connect()'' doesn't return the ''link_identifier'' anymore. (it was not useable with other SQL methods anyway) |