3.3.1 Released

Thanks Tammy!  😀

Tammy,

Are there instructions available on manually updating because I did change quite a few things and if it's simple enough to patch the files, I'd rather do that than try and remember all that I changed in the files.

Unfortunately no.  I've been doing the fixes  in stops and starts because of my time constraints so I don't have any manual instructions.

It'S okay. Thanks. I'll just be careful about not missing any of my changes then. 🙂

I've just updated my testsite to the new release

say Tammy do you want us to post any bugs that we still find in this topic?

I just uploaded the new release, and when I'm logged in and try to view NC-17 stories, I have "Age Consent Required" come up and I can't go on to read the story. When I'm not logged in, the age consent pop-up works just fine. Is there a way to stop this from coming up?

I just finished uploading all the new 3.3.1 files (minus the skins folder) to my server, and I went into the Admin area and the Archive Maintenance/Run Update to run the update, but it says the update's already been completed and no further action is required. The version check still says I'm running 3.3. Am I having a brain fart and I forgot something really obvious, or is there something amiss here?

When you uploaded the files, then went to your website it should have been under site maintenance. Then when you logged in it should have asked if you are ready to run the update. Then it would have updated. You didn't need to go to Admin Maint.-> Run update at all. Afterwards it takes you to the admin screen where it says you are running 3.3.1. Maybe a file didn't get completely uploaded?

I uploaded all the files except skins, install, tinymce, and images.

I got that message, that the site had already been updated. I thought that maybe one of my members had done it because I didn't have maintenance mode on or something, but then I reuploaded /install folder and update.php and went to the admin maintenance and updated and it worked that time.

The site didn't automatically go into maintenance after I uploaded the new files. I tried re-uploading the install/ folder and the update.php (the one in the main directory, not the one in the admin/ directory) and going into Maintenance mode, but it didn't change anything, even when I went to the update link (update.php) or I went to it through the admin panel. I downloaded 3.3.1 again and am reuploading it (minus skins, tinymce, install, and images) to see if that helps.

So far the only odd thing I've noticed is that when I upload it (using Dreamweaver CS3), I get "Synchronization data has not been found for admin.php. Do you wish to continue?" and of course, I click yes. I don't know what "synchronization data" is, though.

Synchronization data... I think I got that error once or twice with Dreamweaver. It has this function where you can "Synchronize", or make the same, both copies of your site: Local and Remote. It takes the newest files from both and makes sure that each have them and they are the same. I dont think the error has anything to do with do your problem though.

I don't think that the site is supposed to go into maintenance mode after you upload the files. A lot of moderators might want to put their site into maintenance mode before they are updating so users can't change things when it's being updated. I don't bother though. I don't think maintenance mode has anything to do with it.

After I uploaded my files, I went to the homepage of my archive, and the admin page.. I'm not sure which one had the link to 'update' the site just showing up to stare me in the face, but I didn't have to look for it. It just showed right up.

I wonder if it was the particular ZIP that I downloaded; I re-downloaded 3.3.1, re-uploaded everything as previously mentioned, and I checked both my eFic sites-- the update worked. When I went to the page, I automatically was taken to the "Do you want to update?" page. So it worked! Not really sure what the problem was in the first place, but it sure was mysterious...

Okay, now I'm seeing something even stranger-- I updated and am properly seeing the current version number 3.3.1, but when I run the version check, it says the current version is 3.3 and I need to update!

The file on this server was not updated. It's fixed now.