I’m currently working on some new extension for NextGEN-Gallery. One target is better support to fetch images via a API similar to FlickR. This idea is born since I have my new QNAP NAS : All my images are now located on my NAS and now I would like to show them in a nice slideshow, search for them, organize them to galleries/albums, access from my NAS WordPress blog and so on…
The first tests are great, but for an easier implementation (in this case JSON) I need a PHP5.2 installation. I know that WordPress itself wait as long as possible to switch to PHP5 exclusive, but I can’t wait anymore.
For Version 1.4.X you need PHP5 for the full power of functions, from today I will not longer support PHP4.
PHP 4 hasn`t been updated for a while now.
Any estimate when NGG 1.4 will arrive?
This year 🙂
So its going to be somewhere between eastern and christmas 🙂
I do not know if I’m posting this in the right place, but I try anyway.
First let me just say, that I find NexGen Gallery to be a super Gallery Plugin for WP that I enjoy using.
But I have one question about the way NG organizes the pictures ( datastructure? )that I do not find logical. I often want to show the same photo in different galleries. Why do I have to make a physical copy of each photo?
I imagine that each gallery could have been a list pointing to photos in one or several catalogues. As it is now, I have to have several copys of the same file to list it under different galleries. I find that a bit unelegant and a waste of space.
Anyway thanks a lot for a great plugin! (ANd if anyone want to take a look at my use of NGGallery and my pictures, please take a look at http://www.ohb.no/foto
Just wanted to come by and thank you for making and maintaining this essential plugin. I’ve featured it on my list of plugins I use here: http://www.squidoo.com/wordpress-plugins-thanks
I have to say that my site lives and dies by your plug-in. It is, hands down, the best gallery plugin for WordPress. The fact that it integrates so well into WordPress means that both my fiance (who hates to have to work in more than one back-end system) and myself are able to quickly and easily get our photos uploaded to our site. I’ve fixed (or sidestepped) most of the issues that folks on the web have discussed having thus far and have arrived at a situation where I want to be able to do the following:
Page Name:
Pictures (containing an “album” called pictures that shows all “sub-albums” that can be clicked on to go to their respective pages)
|_
| Events (containing a sub-album containing galleries of events)
|_
Photography (containing a sub-album containing galleries of photography)
etc etc…
My issue is that I can’t quite figure out how to achieve what I’m wanting…any suggestions?
WP 2.8.1
A NextGENeration Photo gallery for the Web 2.0.
ver 1.3.4
Fatal error: Call to undefined function utf8_encode() in /var/www/localhost/htdocs/blog/wp-content/plugins/nextgen-gallery/admin/functions.php on line 217
I`m crying.
Hi,
Sorry, this isn’t related to this post but I couldn’t see any link to contact you any other way.
I’m using your NextGen widget in a new website i’m building and have found that unlike all my other sidebar widgets which have an H3 title, the NextGen widget displays its title as an H2 heading.
I know I can style the header using CSS, but i’d like to keep the semantic structure of the site as accurate as possible.
Is there anyway you could make an update to your plugin to change this H2 heading into an H3? I can edit the plugin files myself but would have to make the change every time you update the plugin in the future.
thanks,
Greg.
[…] Heute habe ich meinen Webserver auf PHP 5 umgestellt und somit offiziell den Betrieb damit aufgenommen. Bisher scheint alles zu funktionieren. Einzig das WPG2 Plugin fĂĽr Gallery2 sowie die Gallery2 machen rechte Probleme, was mir eigentlich egal sein kann, da ich auf das NextGen Gallery Plugin setzte und nach wie vor zufrieden bin. Dieses Plugin war auch einer der BeweggrĂĽnde, warum ich auf PHP 5 umgestellt habe. Die neuen Versionen/Releases dieses tollen Plugins werden wohl zwingend PHP 5 voraussetzten, wie hier auf der offiziellen Pluginsite zu lesen ist Goodby PHP 4. […]
I’ve switched my plugin (pagebar) to PHP5 with the latest major update … and regretted it! There were so many people complaining that the plugin did not work on their host that I cancelled my decision and re-coded it. Now it PHP4 compliant and has very bad code (_good_ OOP and PHP4 are two different worlds) but I have happy users.
latz
Ce plugin est vraiment une ….. il est bourrer de bugssssssssssssssssssssss!!!!!!!!!!!!!!!
marre de ce plugin! j’ai l’impression que cette version n’a pas Ă©tĂ© tester avant, et que du coup c’est nous les cobaye!
Comment peut on crĂ©er une nouvelle version, et la mettre en tĂ©lĂ©chargement, sans avoir sois mĂŞme vĂ©rifier qu’il fonctionne bien!
J’ai passer, des heures Ă faire mon site, et au finale, je me retrouve avec un plugin, qui fonctionnait très bien avant que je face cette maudit mise Ă jour! (j’ai bien sur rĂ©installer l’ancienne version qui au finale na rien changer,pour qu’enfin ces bugs n’apparaissent plus) Mais voilĂ que cela na rien changer!
J’ai dĂ©sinstaller plus d’une fois, et rĂ©installer plus d’une fois aussi, tout va pour le mieux, puis soudain tout ce met Ă dĂ©traquer! POURQUOI? aller savoir!
Tout ce que je peux vous dire, c’est de n’installer en au qu’un qu’Ă ce plugin, car tout votre travail, ne serais qu’une perte de temps!
bonne journée à tous