Thread

Long story short, I specialize in vBulletin not Expression Engine and I’m having issues upgrading a clients site who runs both vBulletin 4.0 and Expression Engine at the same time i.e. Forums from vB and Home page and Blogs in EE form. I have followed all documentation to a T and it does not upgrade properly and this will now be my fifth time attempting this…

History:

- 1.6.8 to 2.1.1 = Fail, Stated the info in path.php was not correct however path.php was blank and never used, no multiple site manager or the other related to using path.php so why would that be an issue. I read several threads where staff said to do upgrade incrementally i.e. 1.6.8 to 1.7.0 then up to 2.1.1 now see below.

- Due to the failed 1.6.8 to 2.1.1 I deleted everything and simply re-uploaded all backups (timestamps intact for files/attachments/uploads etc etc) so that’s backups of both filesystem and database, it restored with the “System Offline” message on screen just fine. I then proceeded to upgrade to 1.7.0 and the script ran fine, no issues and CP access however this time in 1.7.0 the CP stated:

Notice: unserialize() [function.unserialize]: Error at offset 80013 of 80015 bytes in /home/private/clientsite.com/html/ee/panel/plugins/pi.magpie.php on line 1727

Now, before you go assuming lol.. yes the system folder is renamed panel however in my recent 5 attempts I’ve updated the info in all the locations you commonly post to your customers here in the support forums…

I temporarily removed the error by adding this to htaccess:

php_flag display_errors off

However that only removes me from having to look at it as I navigate otherwise the issue is still present naturally :p.

Just to be clear, I’ve had it named system then I’ve had it panel then I’ve edited the CP settings and the config and the index to reflect the proper $system_path in the previous 5 attempts at this however in the current upgraded 1.7.0 it mocks me with this:

Your system folder path does not appear to be set correctly. Please open the following file and correct this: index.php

Other details…

System is renamed panel and URL structure is this:

http://www.clientsite.com/ee/panel

Blogs are located in:

http://www.clientsite.com/news

I’ve followed instructions in several threads without success is this a bug or am I simply overlooking something perhaps with the fact that the blogs are in /news and that could be the issue here or? What else do you recommend for me to try? I need to upgrade this from 1.7.0 to 2.1.1 and any assistance would be greatly appreciated, thanks for your time.

Sincerely,

Michael Miller Jr

Bump

*Sorry just looking for feedback and I was unsure if EE Staff or Mods worked over the weekend?

Thanks 😉

There is some limited coverage only over the weekend. As to your issue:

... having issues upgrading a clients site who runs both vBulletin 4.0 and Expression Engine at the same time i.e. Forums from vB and Home page and Blogs in EE form. I have followed all documentation to a T and it does not upgrade properly and this will now be my fifth time attempting this…

Do you have a reliable pre-update backup? My suggestion would be to roll back to 1.6.8, make sure that’s working as intended, then try again. Check all relevant permissions, too. Make sure to upload a fresh set of files (including themes), and that all of you add-ons (if any) are compatible with the new version. If you’re running into any issues stop and tell us about them at once.

Are you using .htaccess? Might want to try disabling that for a while.

Hi Miami Beach 411,

Are you able to restore your 1.6.8 files and database again? Let’s make sure the 1.6.8 site is working as expected before trying to go to 2.1.1.

Actually I was able to get it working very early this morning. For some reason the new index was the culprit, I uploaded a backup copy from 1.6.8 and it’s working fine now minus the admincp still shows the error i.e.

no issues and CP access however this time in 1.7.0 the CP stated:

Notice: unserialize() [function.unserialize]: Error at offset 80013 of 80015 bytes in /home/private/clientsite.com/html/ee/panel/plugins/pi.magpie.php on line 1727

I was able to remove that via php_flag display_errors off in htaccess but that indicates to me that something is still up somewhere else and I would like to properly torubleshoot that before attempting 2.1.

My main question is, do you advise I try again from 1.6.8 or continue on with 1.7 and try to upgrade after backing up the current 1.7 site? I feel if the error above is not major I should simply find a remedy for that then upgrade to 2.1 or can we simply leave it in 1.7 form since it’s still secure and run it under the 2.x license?

Miami Beach 411, did you also update your magpie plugin? I’d get 1.7.0 working correctly first, then worry about getting to 2.1.1 later.

Miami Beach 411, did you also update your magpie plugin? I’d get 1.7.0 working correctly first, then worry about getting to 2.1.1 later.

Sue,

I believe your referring to system/plugins/pi.magpie.php is that correct?

If yes then I simply uploaded the one included (originally with 2.1.1 as I was unaware it was recommended just not documented that I should do 1.6.8 to 1.7 then to 2.1 etc) is there another update process for that single plugin alone or you were referring to uploading as updating? I know that after trying the process a few times we were stuck with a non-working blog which of course no one wants so I started troubleshooting tons of things, I scoured many threads and went about checking CHMOD permissions and other things then decided to try overwriting the one file in question as it said the index.php had an invalid system path I overwrote it and badda-bing we were back.

Since some plugins are not compatible in 2.1.1 from what I have read when coming from 1.6.8 or 1.7 for that matter… is it ok to run the current 1.7 under the 2.x license, Gus just renewed and that meant purchasing the 2.x license. With vbulletin you can run a 3.x version under the 4.x license and some are very happy with that seeing as not all like changes or new versions of software etc so that is really my main question atm.

If you believe that one error is coming from pi.magpie.php what is the normal course of action to remedy that?

Sorry Sue as you can tell I’m very new to EE and in particular your site here. I handled some additions to the index via php to integrate vBulletin and EE and pull in new threads and posts from vBulletin into the blog index however other than that I’m very new to the scene and your variables within templates so if I ask questions that most members know the answer to already or have posted before I apologize in advance and again, thanks for the assistance 😉.

is it ok to run the current 1.7 under the 2.x license

The 2.x license allows you to run 1.7 alternatively, yes.

If you believe that one error is coming from pi.magpie.php what is the normal course of action to remedy that?

Replace with the latest version / a fresh file. There is no separate update procedure.