Invision Community 4: SEO, prepare for v5 and dormant account notifications By Matt November 11, 2024
RuneScapez Posted October 27, 2008 Posted October 27, 2008 Hello, I have a couple of quick questions regarding IPB V3. Firstly, with the introduction of the rel='nofollow' tag in the ACP, will it automatically add the tag to existing links or will we have run something to edit each link in the database? Also... Will we have to pay the $60 fee to have our MySQL database converted from IPB 2.3.6 to IPB 3? Thanks :)
bfarber Posted October 27, 2008 Posted October 27, 2008 Hello, I have a couple of quick questions regarding IPB V3. Firstly, with the introduction of the rel='nofollow' tag in the ACP, will it automatically add the tag to existing links or will we have run something to edit each link in the database? This is a tad confusing to explain. While your posts will still look ok if you don't rebuild them upon upgrading to IPB3, you will effectively at some point have to rebuild your posts after upgrading. Reason is, in 2.3 we parsed bbcode on save (so it's stored in the database parsed). In 3.0, however, we parse it on display. So all the bbcode in the database needs to be unparsed and stored that way. On a positive note, you should never have to rebuild posts again in the future after any upgrade, so long as we decide to always parse on display. After rebuilding your posts, since we parse at run time, the nofollow tag will be on existing content as well as new content. And if you turn the setting off, it will not be on existing content (again, when things are parsed on display, changes happen immediately).Also... Will we have to pay the $60 fee to have our MySQL database converted from IPB 2.3.6 to IPB 3? Thanks :) No, this isn't a conversion. So long as you have an active license you will be able to upgrade.
OpenWare Posted October 27, 2008 Posted October 27, 2008 On that note... (I hope you don't mind me chiming in here) I assume, that the posts were saved in two places in the database.. the main posts table holding the "raw" posts, and another holding the parsed post-data that is displayed. I am assuming that since 3.0 will parse-on-display, meaning all our posts will have to be rebuilt after the upgrade, this additional data is therefore redundant and no longer required. As nit-picky as this may sound.. I dont like extra and unneeded files lying around in my IPB folder, nor do I want unneeded data sitting in my forum database. Will the upgrade remove the unneeded data... or will it still be there taking up space. That is, will it be like upgrading from 2.1 -> 2.2 where we just uploaded the new version on top of the old one and ran the upgrade script.. or will we be free to delete the old installation except for conf_global.php and the uploads folder.. and just run the upgrade script. Or will it be like converting from vB to IPB where we would install 3.0 as a clean installation and then convert the older 2.3 install to the new one, meaning we start fresh with a clean database sans any redundent data/tables no longer used by the new version?
RuneScapez Posted October 27, 2008 Posted October 27, 2008 This is a tad confusing to explain. While your posts will still look ok if you don't rebuild them upon upgrading to IPB3, you will effectively at some point have to rebuild your posts after upgrading. Reason is, in 2.3 we parsed bbcode on save (so it's stored in the database parsed). In 3.0, however, we parse it on display. So all the bbcode in the database needs to be unparsed and stored that way. On a positive note, you should never have to rebuild posts again in the future after any upgrade, so long as we decide to always parse on display. After rebuilding your posts, since we parse at run time, the nofollow tag will be on existing content as well as new content. And if you turn the setting off, it will not be on existing content (again, when things are parsed on display, changes happen immediately). No, this isn't a conversion. So long as you have an active license you will be able to upgrade. Read and understood, thanks for clearing this up for me. :)
teraßyte Posted October 27, 2008 Posted October 27, 2008 I assume, that the posts were saved in two places in the database.. the main posts table holding the "raw" posts, and another holding the parsed post-data that is displayed. No, currently posts are saved only in 1 place and are saved parsed. With the upgrade to IPB 3 I suppose the upgrade script will convert all posts from parsed to un-parsed like they were in IPB 2.1.
TCWT Posted October 27, 2008 Posted October 27, 2008 I hope the script can be run in SSH without any issues.
Stepashka Posted October 27, 2008 Posted October 27, 2008 I hope the script can be run in SSH without any issues. There wasn
TCWT Posted October 28, 2008 Posted October 28, 2008 The ssh rebuild is the same speed as web php build. :(
Recommended Posts
Archived
This topic is now archived and is closed to further replies.