I'm having various severe issues with wpg2 version 3.x, mostly with the image choser. Basically it ceased to work, completely. On one blog I get:
Quote:
Fatal Gallery2 Error: Cannot activate the Gallery2 Embedded functions.
For WordPress users, Validate WPG2 in the Options Admin panel.
For other platforms, please verify your Gallery2 path in config.php.
In the popup when I click on the wpg2 button. Note that the validation thing in the options panel doesn't show any problems at all, and all settings seem to make sense to me. On another blog, the button doesn't even show; instead, I get:
Quote:
Warning: Invalid argument supplied for foreach() in /home/_common/2.3-plugins/wpg2/wpg2functions.inc on line 397
Fatal error: Cannot unset string offsets in /home/www-nils/htdocs/gallery/modules/core/classes/GalleryUrlGenerator.class on line 559
in the "write post" page. It all used to work quite nicely with wpg2 2.x.
I do have one weird setup in that my ~/wp-content/plugins and ~/wp-content/themes are symlinks to directories under /home/_common/ (as you can see above). This does sometimes cause problems with plugins that do not detect their paths relative to the document- /server root correctly, unfortunately wpg2 is way too big for me to try to figure out where to hunt this down. (I already did have this setup when using the "older" wpg2 and had no issues, so something must have changed in wpg2.)
I do not really wish to downgrade again, because 3.x is much nicer than 2.x so any help would be appreciated.
Posts: 1378
I am going to move this into the G2 Image forums, I am pretty sure the symlink is causing the G2 Image to not find the WPG2 Function libraries but Kirk may be able to provide you with a more exact answer..
____________________________________
Wordpress / Gallery2 (WPG2) Plugin, , WPG2 Documentation, WPG2 Demo
Posts: 492
Sorry for the delay answering this. I've been away from G2Image development for a while due to real life. Did you already get this sorted out?
The 2.x versions of WPG2 had G2Image in the TinyMCE directory under /wordpress/wp-includes/ so your symlinks didn't matter then. But asking people to install multiple directories led to other problems, so when the TinyMCE hooks were added for WP 2.3, we moved G2Image into a subdirectory under WPG2, so now when G2Image tries to find its way around, it's lost because it assumes that it's in wp-content/plugins/wpg2/g2image.
Is something really driving you to use the symlinks? If so, you'll have to hard code in the correct paths in g2image/init.php. Let me know if you're still trying to get it to work, and I'll take a few minutes to figure out what you need to change.
Kirk
____________________________________
G2Image Documentation, G2Image Demo Page, My Family Website