PhotoPost Community - View Single Post - Layout Problem after 3.2.1 to 5.11 upgrade

sonick · June 23rd, 2005, 07:18 AM

Greetings,

First, the requested variables for posting support requests:

OS: Linux
Distro: Red Hat Enterprise Linux ES release 3
Kernel: Linux - 2.4.21-32.0.1.ELsmp #1 SMP - i686 athlon i386 GNU/Linux
PHP: 4.3.11
MySQL: Ver 14.7 Distrib 4.1.9, for pc-linux-gnu (i686)
Host Type: Dedicated
Server Ownership: Leased unit from monstercommerce.com, CoLo resident
Host and Site Admin: Myself
Gallery URL: http://www.cycleforums.com/photopost (Currently offline due to improper layout)
vBulletin Integration: Yes, vBulletin 2.2.8
Note: In order to view the gallery as it is currently, I will have to work with someone in concurrent communication to flip the board on/off so it can be viewed. I cannot enable the board for "a while" as the many users the site has will return and attempt to interact with it as usual. I require that the upgrade be working and complete before turning the users loose on it.

-
I am writing to report an issue discovered post-upgrade from 3.2.1 to 5.11. The upgrade.php mechanisms themselves were all performed without a hitch, 100% success rate from all operations during each stepped revision upgrade within the script. Once the final revision was reporting 5.11 and the upgrade.php output stated that the upgrade was complete, myself and the other root administrator for the site went to check the gallery to assure everything was working properly, and immediately we were greeted with a layout that was absent any visible table borders, font types and sizes were wrong, and various other layout options that prior to this version were set manually with the photopost 3.2.1 admin panel (ie: colors for various layout options express in hexadecimal, font names and sizes explicitly declared, etc.)

To summarize, absolutely everything that I am aware of is working properly EXCEPT the inheritance of our past layout design as was set in the previous 3.2.1 admin panel. Databases are all working fine, authentication is fine, headers are fine, footers are fine, ImageMagick operations are fine; everything EXCEPT the appearance as was setup prior through the 3.2.1 admin panel is working properly.

I have searched forums, support faq, code comments, etc. for the answer as to what I may be missing to get our prior look and feel into the current template system, but by this point the prior layout values themselves had been dropped from the database. I did save a copy of the prior values from database.settings from the old database, and of course I have a full backup of the 3.2.1 database as stood before upgrade to 5.11. It appears that in order to create a 5.11 stylesheet containing the values we used prior, the vbulletin integration has to be turned off. With vbulletin integration on, it appears that we need to somehow pull these values from templates in some fashion. Our site requires that the vbulletin integration be turned on; without the cross-authentication alone the big selling point for us on photopost a couple years ago would be rendered moot.

In final summary, I will say that I am a long-time UNIX and Network Admin, but I'm pretty green when it comes to layer 7 and the site code itself. I had expected that the current layout/cosmetic settings in the 3.2.1 database would be culled and somehow imported into the 5.11 environment; whatever mechanism that may be with vb2 integration enabled. If it was supposed to happen, it did not in our environment. Again, the upgrade.php reported 100% rate of success during each step (and there was a considerable number of steps). Prior to this, the software performed flawlessly, and I remain confident that this issue will be solved regardless of whether it's a shortcoming in such a large-step upgrade, or even if it's an egregious oversight by myself. I'd prefer the latter to tell you the truth, I'm perfectly OK with making a stupid mistake if it would get our beloved photo gallery back quickly! I would not have even upgraded to 5.11 if it hadn't been for the published vulnerabilities in the prior code, the functionality was still perfect for our needs. Since we're not yet on vb3 (what a nightmare that will be), a lot of the value-add from 5.11 is moot in our case. In any case, I'm glad to support the software and continue to run it if this layout problem can be solved. All I want is for our prior look & feel to operate properly in the 5.11 environment.

Any and all assistance and input is appreciated and will be taken into account. Sorry this post was so wordy, I don't want to miss any needed information and I have severe spaz/ADHD wordiness problems so it's inevitable in any case

Thanks,
Jayson
sonick@sonick.com

http://www.cycleforums.com
http://www.big-boards.com/highlight/279

June 23rd, 2005, 07:18 AM	#1 (permalink)
sonick Registered User Join Date: Jun 2005 Location: Valley of the Sun Posts: 11	Layout Problem after 3.2.1 to 5.11 upgrade Greetings, First, the requested variables for posting support requests: OS: Linux Distro: Red Hat Enterprise Linux ES release 3 Kernel: Linux - 2.4.21-32.0.1.ELsmp #1 SMP - i686 athlon i386 GNU/Linux PHP: 4.3.11 MySQL: Ver 14.7 Distrib 4.1.9, for pc-linux-gnu (i686) Host Type: Dedicated Server Ownership: Leased unit from monstercommerce.com, CoLo resident Host and Site Admin: Myself Gallery URL: http://www.cycleforums.com/photopost (Currently offline due to improper layout) vBulletin Integration: Yes, vBulletin 2.2.8 Note: In order to view the gallery as it is currently, I will have to work with someone in concurrent communication to flip the board on/off so it can be viewed. I cannot enable the board for "a while" as the many users the site has will return and attempt to interact with it as usual. I require that the upgrade be working and complete before turning the users loose on it. - I am writing to report an issue discovered post-upgrade from 3.2.1 to 5.11. The upgrade.php mechanisms themselves were all performed without a hitch, 100% success rate from all operations during each stepped revision upgrade within the script. Once the final revision was reporting 5.11 and the upgrade.php output stated that the upgrade was complete, myself and the other root administrator for the site went to check the gallery to assure everything was working properly, and immediately we were greeted with a layout that was absent any visible table borders, font types and sizes were wrong, and various other layout options that prior to this version were set manually with the photopost 3.2.1 admin panel (ie: colors for various layout options express in hexadecimal, font names and sizes explicitly declared, etc.) To summarize, absolutely everything that I am aware of is working properly EXCEPT the inheritance of our past layout design as was set in the previous 3.2.1 admin panel. Databases are all working fine, authentication is fine, headers are fine, footers are fine, ImageMagick operations are fine; everything EXCEPT the appearance as was setup prior through the 3.2.1 admin panel is working properly. I have searched forums, support faq, code comments, etc. for the answer as to what I may be missing to get our prior look and feel into the current template system, but by this point the prior layout values themselves had been dropped from the database. I did save a copy of the prior values from database.settings from the old database, and of course I have a full backup of the 3.2.1 database as stood before upgrade to 5.11. It appears that in order to create a 5.11 stylesheet containing the values we used prior, the vbulletin integration has to be turned off. With vbulletin integration on, it appears that we need to somehow pull these values from templates in some fashion. Our site requires that the vbulletin integration be turned on; without the cross-authentication alone the big selling point for us on photopost a couple years ago would be rendered moot. In final summary, I will say that I am a long-time UNIX and Network Admin, but I'm pretty green when it comes to layer 7 and the site code itself. I had expected that the current layout/cosmetic settings in the 3.2.1 database would be culled and somehow imported into the 5.11 environment; whatever mechanism that may be with vb2 integration enabled. If it was supposed to happen, it did not in our environment. Again, the upgrade.php reported 100% rate of success during each step (and there was a considerable number of steps). Prior to this, the software performed flawlessly, and I remain confident that this issue will be solved regardless of whether it's a shortcoming in such a large-step upgrade, or even if it's an egregious oversight by myself. I'd prefer the latter to tell you the truth, I'm perfectly OK with making a stupid mistake if it would get our beloved photo gallery back quickly! I would not have even upgraded to 5.11 if it hadn't been for the published vulnerabilities in the prior code, the functionality was still perfect for our needs. Since we're not yet on vb3 (what a nightmare that will be), a lot of the value-add from 5.11 is moot in our case. In any case, I'm glad to support the software and continue to run it if this layout problem can be solved. All I want is for our prior look & feel to operate properly in the 5.11 environment. Any and all assistance and input is appreciated and will be taken into account. Sorry this post was so wordy, I don't want to miss any needed information and I have severe spaz/ADHD wordiness problems so it's inevitable in any case Thanks, Jayson sonick@sonick.com http://www.cycleforums.com http://www.big-boards.com/highlight/279