WPReady

Hi acekin,
thanks for your comments.
I guess what you said is right. I’m not giving full attention to the forum in these days. My apologies for that.

After the next release, I’m going to give full support to anyone who need some help. That will be before May. I would hate to start something and then let it derail because some sort of perceived indifference.

Currently we are building a wikipedia around the plugin. I say ‘we’ because I’m confident many other will be contributing to the idea, similar of what is happening just right now.

I’ve been looking the forum from time to time and I believe the community deserves a better support from my part. Many other developers are currently helping without even mentioning, so this is a big THANKS to them, in a way. For other side, I understand your feelings about the support. In some way is reflecting what many users needs, even the plugin is free or not. So this is a thanks to you to letting me know.

If you want to stick with NextGen, please be my guest. Nextcellent is trying to close a gap to those people which found some trouble using the new version. And I was (and I am) one of them.

The plugin is also trying to be a stable one, and when I’m saying ‘NextCellent is an alternative to most people so they can sleep with peace of mind’ (see readme.txt) I really mean that.

I just hope to meet the expectations!

Again, thanks for your comments.

Hi there,
next release has this request solved.
I’m merging last requests to release it.
Stay tuned.

Hi ritaszabo77,
the error seems to be due ImageMagick library is selected.

Check in the Settings -> General
Option ‘Select Graphic Library’ set to GD Library

Hi chrisborgman,
WP Supersized assumes the plugin is folder nextgen-gallery. It is using a similar practice mentioned on http://wpgetready.com/2014/01/nextgen-public-uploader-working-with-nextcellent/
…
if (is_plugin_active(‘nextgen-gallery/nggallery.php’) && method_exists(‘nggdb’,’find_all_galleries’)) {
…
Which is not bad, but NextCellent can’t be detected.

There’s a workaround. Renaming NextCellent folder on plugins folder to nextgen-gallery should be enough.

Hi Whale74,
I’ve been reading about your implementation and what webaware pointed out.
I also came across with http://code.google.com/p/nextgen-gallery/issues/detail?id=375 an old request time ago.

I guess it’s time to make improvements on nggtags shortcode.

Hi z-m-b,
glad to help you. Thanks to Websiteguy too!
I guess is the right time to make a wikipedia with these incidents…

By the way, could you tell us what is the plugin exactly?
Thanks!

Hi z-m-b
At first, many things are ok. The slideshow uses a javascript code , which in turn makes a callback. So far, this is working as expected (even though no images are displayed). A manual invoke on the callback with the given parameters returns correct JSON info. I would discard the case where is misconfigured and I could suspect that something is going on on the javascript side.

We would need to simplify the scenario, since currently the page has more than 20 javascript files running at the same time and maybe there is some conflict preventing the plugin to work properly.

Hi Websiteguy,
First, I appreciate your contribution on the forum. Thanks for your help.

1. I saw your plugins an video, that would be a good idea.
2. Agreed
3. I’m agree with you and I’ll be following the forums. I also viewing some requests and solutions like http://wpgetready.com/2014/01/nextgen-public-uploader-working-with-nextcellent/ . This is an answer to older requests.