Suggestion for NextGen

  • I believe that many people must agree that the status of NextGen plugin is critical. So I have a couple of suggestions that may be considered.
    First to see that the critical problems: high CPU and memory usage, code written in hurry, rapidly inserts transient values in wp_options table (I got more than 100.000 inserts in few days).
    My suggestion is to start again from version 1.9.13.

    It’s much more better to slowly continue to upgrade the new options and add new features, but fill a script with unnecessary carousel menu, heavy code and framework. Designers (and many users) know that it is far better top navigation menu (optional: drop-down) than ugly carousel. So is clearer, faster and more flexible. In my opinion, remove carousel completely and no one will complain for sure (also no need external .js and .css just for useles carousel).

    Important: use the old code logic as base – means, remove pope framework and bunch of files. WordPress already has a good and flexible hook system, so additional coding (“framework for framework”) only complicates things and creates the possibility of new bugs.

    Instead of adding framework, I belive it is better to add new options (for example image tagging will be awesome or more options for editing images or adding image effects…there are lots of possibilites).

    Correcting thousands of current bugs is Sisyphean task, and requires a lot of time and nerves, and I believe that it will not end well.

    Also, note that high memory usage is not (usually) server problem, but plugin. Increasing memory from php.ini is not a solution (and may lead to suspend your account).

    https://www.ads-software.com/plugins/nextgen-gallery/

Viewing 5 replies - 1 through 5 (of 5 total)

  • I definitely agree and the last segment of this post should definitely be empathized. Thankfully I have my own dedicated server so I’m not worried about raising values, but the values that I did have to raise my php.ini file to just seem highly unnecessary, especially considering the fact that resource consumption was still quite high when importing folders. My skills aren’t good enough to think of a good solution for those issues, I know just enough to be able to identify the issue, and this plugin is the only thing on my server which uses so much resources. Seeing all that happen on my dedicated box, I worry about how badly shared server users are impacted. I just wanted to add that in, the above was a great post and I hope that things can be improved here.

    Thread Starter eevan79

    (@eevan79)

    I know how much can be frustrating for users and developers when something like this happens. Because the only logical solution I see what is written above.

    I hope that the development of this plugin will finally move in a positive direction.

    I worry about how badly shared server users are impacted

    I’m on a shared server and there was no particular impact.
    The only thing I noticed is an increase in the DB dimensions.

    Thread Starter eevan79

    (@eevan79)

    50.000 – 100.000 inserts per day is not a small thing. This is temp data that is not flushed periodically.

    I tested NG 2.x on multiple servers. It all depends on server performance and other users. Somewhere websites slowed down for 2-5 seconds, somewhere for 20-30. As for me, neither option is not an option. Gallery widget creates lot’s of queries (overall 80-150 additional queries per page load thanks to the new version of NGG).

    Thread Starter eevan79

    (@eevan79)

    To (try to) solve so many problems and conflicts with other plugins that use jquery:
    in every .js put

    jQuery.noConflict();
    var $j = jQuery;

    Than replace $ with $j everywhere. eg $j(function(){ //…
    Still this will not solve problems with lots of queries (116 on homepage and 207 on gallery page. Earlier I don’t have more that 40 queries) and problems with CPU/memory usage.
    No offence, but I think that you are wasting your time…

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Suggestion for NextGen’ is closed to new replies.

Tags