05-09-2008, 09:06 PM
|
|
Head Plog
Admin
|
|
Join Date: Dec 2005
Posts: 5,324
Comments: 25
|
|
PhotoPlog Pro v.2.1.4.8 Released
PhotoPlog Pro v.2.1.4.8 Released
Requirements- vBulletin 3.6.0+
- PHP 4.3.3+
- MySQL 4.0.16+
- PHP with GD2
- Safe Mode Off
New Features- This is a maintenance release
- Changes for CSRF protection (more info here)
- Additional plugin for merging members
- Different handling of editor JavaScript
Changed Files - functions.php
- selector.php
- settings.php
- upload.php
Changed Templates- photoplog_album_form
- photoplog_album_select
- photoplog_block_list
- photoplog_category_form
- photoplog_comment_form
- photoplog_delete_form
- photoplog_edit_form
- photoplog_edit_select_category
- photoplog_expunge_form
- photoplog_file_list
- photoplog_quickreply_form
- photoplog_rate_list
- photoplog_remove_form
- photoplog_report_form
- photoplog_search_form
- photoplog_slideshow_form
- photoplog_slideshow_page
- photoplog_upload_form
- photoplog_upload_select_category
- photoplog_view_file
New Phrases - None - see this thread for language packs
How-to Upgrade (from Pro v.2.1.4.7)- FTP the four PhotoPlog PHP files listed above in ASCII mode to your server, overwriting old files
- Revert the twenty PhotoPlog templates listed above via the ACP, if changed from their originals
- Re-import the PhotoPlog product XML file via the ACP (do NOT uninstall, do allow overwrite)
- Note: changed PhotoPlog templates will not be overwritten by reimporting the XML file
- See the main README.txt file in the ZIP package for further details
Special Note- If you happen to upgrade vBulletin, then delete the vbulletin_textedit.js file from inside the PhotoPlog /images directory if present (do NOT delete the vbulletin_textedit.js file inside the vB /clientscript directory) and PhotoPlog will regenerate the file for you
Discussion- PhotoPlog Pro v.2.1.4.8 discussion here
__________________
Please use the forums for support, feature requests, and similar such things. Support does not include custom code, custom template edits, or third-party modifications. PMs and emails to me should be for private information only, such as login information. If you PM or email me a support question, chances are good that I'll ignore it. Thanks.
While the work or play is on, it is a lot of fun if while you are doing one you don't constantly feel that you ought to be doing the other. -- Franklin Pierce Adams
|