Posted 4 years ago #
Hi, I need help with working out why my NGG slideshow widget has stopped working. I have upgraded to your latest version.
I get a blank screen where the slideshow appeared. I have tried deactivating and re-activating the plugin and re-deployed the widget too. But still it does not work.
Any Ideas? Thx
Try to reupload all files manually again...
Posted 4 years ago #
Yes. Thx that worked.
Does this mean there is something wrong with the automatic upgrade? for NGG??
Yes there is something wrong, I tried to catch it but didn't find it. In 80% of my download it works, but sometimes not...
Posted 4 years ago #
I'm having the same problem - I upgraded - slideshow broke. Uninstalled and deleted the plugin and pout .93 back, still didn't work - put .94 back with the functions.php bug fix, still broke - theodyc.com - not sure what to do now
I can see the slideshow from here...
Posted 4 years ago #
woke up this morning with no problems as well - how bizarre!
Posted 4 years ago #
Hello Alex,
I reupload the plugin manually but this not work... What happen???
Please post a link as example
Posted 4 years ago #
well .. noone actually seemed to take a look at my posting - so i'll try it here:
I've almost the same problem - the Slideshow never started working - i don't know why ... the picture list works
http://www.juern.de/?page_id=8
any suggestions?
kg
J-C
Posted 4 years ago #
Hello Alex,
My blog is http://www.rubenmejias.es and you can see the slideshow in the middle-right sidebar.
Thanks!
Posted 4 years ago #
@ rmejias .. this is EXCATLY the same problem I'm stuggeling with ...
The file nggextractXML.php returns a Error 403. Check the permissions...
Posted 4 years ago #
well - i think all permissions are set:
http://juern.de/wp-content/plugins/nextgen-gallery/nggextractxml.php
and I tried the "location"-paths ... everything seems to work ????
Posted 4 years ago #
OMG ... i fixed it ...
filesnames were lowercase > nggextractxml.php instead of nggextractXML.php
Posted 4 years ago #
The file nggextractXML.php have 777 permission code... What code need for resolve the 403 error??
Posted 4 years ago #
ever tried to make the whole gallery-directory to 777 ???
Posted 4 years ago #
SO what was the solution for rmejias? I can't find the answer here, but see that his slideshow is now working?
It would be fine if responses were given here and not directly to the users.
My slideshows won't show up, take a look at http://www.ertzgaard.net/geir, both in main area and in the sidebar.
Posted 4 years ago #
@ GEIRSAN ... hum - have you tried to remove the spaces in your filenames???
like this:
http://ertzgaard.net/geir/wp-content/gallery/from-asia-with-love/Geir bilder Asia 007.jpg
into this:
http://ertzgaard.net/geir/wp-content/gallery/from-asia-with-love/Geir_bilder_Asia_007.jpg
????
Posted 4 years ago #
Hi
I'm also having a problem with slideshow. Using NGG 0.95 with WordPress 2.5.1. I just get white space where the slideshow should be. I have manually reloaded NGG Gallery to the server and have set permissions on swfobject.js and imagerotator.swf to 755. No change - still white space. If I right click on the white space I get a menu as if the slideshow were there.
This is the link Braidburn photos
Any suggestions as to how to resolve this would be much appreciated.
@AttractMore
The file nggextractXML.php could not be found in your case
Posted 4 years ago #
Hi Alex
Thanks for your reply. I can see a file called nggextractXML.php under wp-content/plugins/nextgen-gallery with permissions set at 755. It has 56 lines of code. Have I got this file in the wrong place ?
Thanks
Posted 4 years ago #
here's a bit more info ... The error message produced on the server reads
Premature end of script headers: /home/braidbur/public_html/wp-content/plugins/nextgen-gallery/nggextractXML.php
SoftException in Application.
Any ideas anyone ??
Thanks
Posted 4 years ago #
Ah ha !! Fixed it ! The problem was that the folder wp-content was writable by group and world - permissions set to 777. Don't know why that was or why it prevented the slideshow from working. However, setting permissions to 755 fixed the problem immediately. Phew.
This topic has been closed to new replies.
