Print

[Nitallica]

I've searched through the various threads here detailing the "Fatal error" error, but I'm not sure if it's a CPG bug; so I wanted to check to see if anyone else here had experienced anything similar?

My specs:
    * OS: Windows 2000 Advanced Server
    * Web Server Software: IIS 5.0
    * GD/GD2/ImageMagick: ImageMagick
    * PHP ver: 4.3.10 (but will upgrade tomorrow to 4.4.1 (I bookmarked the php4.4.1 error threads just in case ))
    * BB Integration: none
    * Themes: default ones that came with 1.3.4
    * Major Errors: Hangs on upgrade.php execution.  I looked in phpMyAdmin and database appeared untouched.  All tables had cpg134_ prefix and I didn't see any new fields.  However, the webserver hung up after executing upgrade.php in browser and had to be rebooted before I could access the database or anything at all on the server.
    * Client OS and Browser: XP SP2, Firefox 1.0.7
    * Fresh install or upgrade: Upgrade from 1.3.4


Other notes:

This is an install for one of my clients.  I backed up everything prior to upgrade.  After upgrade failed, I wiped everything out and installed a clean copy of 1.4.1 (much to my client's chagrin) and it appeared to be fine.

I know the beta is unsupported, and I stressed that to my client.  They may be willing to hold out for a stable release, so I'm pushing hard.

However, I'm wondering if this could be an IIS problem?  The client was happy with 1.3.4, but wanted multiple categories -- hence the suggestion to go to 1.4x.

Is anyone running 1.4x in a Windows/IIS environment?  And if so, did you experience this problem?

Thanks!

[Joachim Müller]

did you use the most recent cvs checkout?

[Nitallica]

did you use the most recent cvs checkout?

Not at the time of post.  I was using the 1.4.1_beta listed in your downloads section.

However, I did run across the handy dandy tortoisecvs article last night so I downloaded and installed 1.4.2 this morning.  (great tut btw, bookmarked! )

Also, I was looking at the update.php file last night and noticed that it looks to see if the plugins directory exists (and if not to create it).  Being that I was on 1.3.4 it did not exist, and I'm wondering if it freaked because maybe Windows/IIS handles the directory creation differently as far as permissions and such (I'm no expert, so I'm guessing ), so I created that directory this morning prior to install.

1.4.2 is up and appears to be running fine. (client is happy, yay!!  hehe   )

Thanks!

[Tranz]

Thanks for letting us know so we can keep that in mind, Nitallica.

[Nitallica]

Thanks for letting us know so we can keep that in mind, Nitallica.

No problem.