Jyosua

Thanks to some external help, the issue was identified to be that my redis cache hadn't been flushed prior to attempting the upgrade. Since I had done this upgrade and tested it before on the staging server before attempting to promote it to prod, the redis cache already had objects from 4.7.6 in it, despite the database reflecting the actual, older version. Although this didn't happen to me on the dry run, I did have other errors because the new server originally didn't have redis on it when I first started testing this upgrade, while the old server did. Lesson learned: always disable caching prior to upgrades. I kinda wish that was in big bold letters in the upgrade manual, though...

I'm pretty certain something, somehow is marking the forum as already upgraded even though it's not. Exactly what files determine whether or not it sees an upgrade available? I'm extremely tired right now after fighting with this for hours, after having already spent over 20 hours across the past couple days working out the details of this upgrade. I would like to resolve this before I need to go to sleep for work and my site is down because of this issue at the moment. I can't really use the admin CP at the moment for any of its troubleshooting tools because it's broken as well. I checked the logs and see errors like this: I would assume those errors are because the upgrade hasn't been executed, though.

@Marc Stridgen I reuploaded again and nothing changed. Still the same error message.

I'm going to just unzip locally and scp upload again I guess, but that's a lot slower than unzipping on the staging server directly, so it will take some time for me to see if it changes anything or not.

To be extra clear, what I actually did was scp to upload Invision Community.zip to the staging server, then ran unzip Invision\ Community.zip -d invision cp -R invision/ips_c1ed4/* htdocs/ where htdocs is my site root directory.

Are you sure it's not just because my server's IP changed after already successfully upgrading once?

Sure. My site is normally hosted at forums.serenesforest.net. I stood up a new server at forums-staging.serenesforest.net with an upgraded version of PHP and a clone of my MySQL database on an upgraded version of MySQL, then copied all of the site files to the new server. After changing the conf_global.php to reflect the staging URL and changing the MySQL database endpoint, I downloaded the new version of Invision Community from the client area and uploaded the files to the staging server. I then executed the upgrade from https://forums-staging.serenesforest.net/admin/upgrade/index.php and after it completed, I changed the license key to be my test site license, fixed the skin issues, and downloaded the skin xml so I'd have it when upgrading for real. After this, I backed everything up, set the site at forums.serenesforest.net to offline, recloned the production database (because it had been several days and people were using the site during that time), and repeated the process from the start. However, once I went to run the upgrade again after uploading the new Invision Community files, I got the error in the screenshot above.

I just got through doing a test upgrade and figuring out how to fix all the issues with our skins and server configuration. Once I cloned the server again and recopied our original prod files with the real database in the background, ready to do the production upgrade, I'm hit with this message... any way to fix this? I did all this pre-work with testing explicitly to avoid extra downtime...

Thanks, this is exactly what I would have wanted. I wonder why there isn't a link to this part of the documentation from the getting started? I think it'd be good to direct people there if they want to read in further detail, since the title of that dev docs page doesn't really yell "templates!" to me.

Yep, that was the issue. Thanks for the help! Is there somewhere in the dev docs where this is documented? I did some googling and skimming of the docs, but I didn't see anything that looked like it'd explain the full behavior of the template arguments.

I'm attempting to upgrade to the latest version of the forum software, so I'm porting over some of our customizations, but for some reason I can't get the theme to load a custom template file. In forums>front>topics>postContainer, on line 92, I've added an else condition to load a template bit: {{if !$comment->isAnonymous()}} <li data-role='group'>{expression="\IPS\Member\Group::load( $comment->author()->member_group_id )->formattedName" raw="true"}</li> {{if \IPS\Member\Group::load( $comment->author()->member_group_id )->g_icon }} <li data-role='group-icon'><img src='{file="$comment->author()->group['g_icon']" extension="core_Theme"}' alt='' class='cAuthorGroupIcon'></li> {{else}} <!-- this is the else --> {template="memberBadge" app="core" group="global" params="$comment->author()"} <!-- this is the template --> {{endif}} {{endif}} That template, memberBadge, resides under core>global>global. For whatever the reason, I can't get it to load, even if it's just static html in the template or text. If I put text like "test" under the else condition instead, I see it displayed under the member group name, but if I put nothing but that "test" text in the template, it doesn't display. This worked just fine in the old version, so I'm not sure what I'm missing.

[quote name='tera

FYI: THis no longer works on 3.1.0

I noticed when I upgraded to IPB 2.3.6, extra linebreaks were left behind when quotes were stripped, after you quote a post containing quotes. I opened a ticket about this, and they pointed me to the sources/classes/post/class_post.php file, which had the linebreak stripping line commented out. I uncommented it, however, that removed ALL linebreaks, which wasn't desired either. Instead, I resolved my issue by leaving that line commented out, and instead inserting the following before the quotestripping line: $tmp_post = preg_replace( "#(?:\n|\r|\r\n)(\ It effectively removed any extra linebreaks left behind from the quotestripping. You could integrate this into the quotestripping function, but I decided not to because I may want to change the way this is handled on my forum later. Anyways, I just wanted to let you guys be aware of this issue. :) I didn't post this in the bug section because it's not a bug per se, but I'm suggesting it be added.