eevan79
Forum Replies Created
-
I realize that you are in a difficult position. As for me, no problem because I always make a backup, but I believe that other users may have problems.
I just re-tested it locally and online. Media library does not appear, it is likely a javascript conflict.
Thanks for the good will to help, but I do not believe that I will install a new version soon on a productive site. No offence.
Also, a lot of queries appears on the Gallery view page (front-page). From 34 to 217 queries (displayed 1 album with 10 galleries).Just saw 2.0.14 version.
When adding post:
Now you can say goodbye to Media library when you add/edit post. There are no images (until you disable plugin).When you click on a NextGEN button above textarea to add album/gallery into post, nextgen will simply eat your resources – enormous CPU and memory usage, until your server will (probably) hangup.
People probably just want to add gallery/album into post with few clicks. Earlier we can do that with simple and fast form with few clicks.
Now you must face with heavy and slow interface that can freeze your server, just to add one album or gallery into post/page.Queries on gallery view (list of 10 galleries): 216 queries for one page load.
Transients for displayed galleries seems fixed (no more rapid inserts into database). Still, not even close to 1.9.13…
@chip_88, it depence of your template layout, but you can do the following:
open style.css of your theme and add:.ngg-thumbnail {
margin: 0 auto !important;
text-align: center !important;
float: none !important;
}If you want to center titles add:
.ngg-albumtitle { text-align:center !important; margin: 0 auto !important; }
—–
I just tested image management when adding posts (NGG version 2.0.12). It’s totally broken. Earlier it was much faster, better and more practical and most importantly it worked.
When you click on gallery button earlier it displays simple chained drop-down box to select gallery, album or single image (with Ajax calls). It was very practical, fast and good.
I am so disapointed with a new look when adding images, gallery or album. First it hangs server or even crash when you try to save/select form. Somehow, I managed to select the gallery, add to post and click save (after 2 server hangs). Broken image appear in wordpress textarea (probably placeholder for gallery). Finally, I wanted to update post to check how it looks like, but Update button is disabled (probably because server hangs earlier).
Media library still not working (when you want to add image in post from media library).
From simple form for adding gallery from 1.1.93, they creating something robust, complex, slow and not practical. Also, placeholder was simple…like [albumid=1], now it inserts broken image placeholder (and more code). I simply can not understand why they try to fix/improve this when it was working perfectly.Open wp-config.php and add the following:
define(‘WP_MEMORY_LIMIT’, ‘128M’);
Do rollback then remove this line.
@chip_88,
I suggest you to stay with 1.9.13 until stable version out, but it’s all on you. Then read other user comments and reviews to see if the new version is stable and without bugs (and is optimized). During that time, you can test everything locally (not on production site).
About new features you can always check the changelog, but I didn’t noticed any major features in the new versions.@mellis2718, how you can’t login (wrong password, blank page or else…)?
Try to backup database first, then make a copy of NGG and delete original. Finally, upload the version you want. Be sure to always have a backup before deleting files and/or data from database.I just did a quick test for NGG 2.0.12 and compare with 1.9.13.
Homepage – total queries (and average page load time) – same other plugins and settings:
2.0.12 – 116 queries (3.5 sec)
1.9.13 – 48 queries (0.8 sec)
Only one entry for displayed galleries (seems fixed, but need more testing).“Gallery Settings” and “Other Options” -> accordion menu (ugly, in my opinion). It was much better and clearer before.
Still bug with Manage Album option in Admin panel – Contents of Albums IDs displays over “Select gallery” box. Not a big deal, but it looks ugly and it’s not happened before.
“Hotfix“: nggadmin.css (/products/photocrati_nextgen/modules/ngglegacy/admin/css/)
find:
.groupItem .item_top {
and add just before closing } and change height to height: 100%;
find:
div .groupItem {
change width: 295px; to width: 100%;
(and optional increase line-height). Also add:word-wrap: break-word;
Now albums are displayed in Album ID box (not over other boxes).
It seems that the options are fixed, because now load faster. However, 1.9.13 is still faster and optimized, but fixes are noticeable.
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).
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.
As far as I know the problems are after 1.19.13. version.
With 2.0.7: high CPU usage (and site drastically slow down including backend), NextGen 2.x rapidly inserts temp files/junk in wp_options table, so that the database grows over 150MB in just few days. This is major problems that could cause your account to be suspended (by your webhost)…small bugs I didn’t mention but there are lots of.
2.0.11 brings even more bugs.Unfortunately, I think it can not be fixed any time soon (specially if it continue to use the same logic and framework).
This is how I rolling back to 1.9.13:
– Backup DB (I used MySqlDumper, but you can do it with other mysql tools like phpMyAdmin)
– Backup plugins folder
– Manually delete NextGen 2.11
– Upload 1.9.13Result: website runs 10x faster (including backend). Image upload working fine, no more garbage in database (wp_options table had more than 200MB in few days thanks to NG 2.x), NG options in backend working fine (faster and no more “nested” layout for albums and galleries), many other bugs removed from NG 2.x…also very important: CPU usage decreased a lot after rolling back.
And finally I “cleaned” DB that NG 2.x made:
DELETE FROM
wp_optionsWHEREoption_nameLIKE (‘displayed_galleries_%’);Tested on 5 sites (with different themes) powered by WP with NG plugin.
On every few hours I set the script to delete junk that make NG
$del1 = $wpdb->query( “DELETE FROM
wp_optionsWHEREoption_nameLIKE (‘displayed_galleries_%’);” );Mainly because of the new version of NextGen (2.x) that killed this plugin. I just removed 2.x and upload stable V1.9.13 after which my site worked 10 times faster without bugs that provide NG 2.x .
This is my experience: I first update the wordpress and then the NextGen plugin to 2.0.11. Entire site is drastically slowed (including backend). Images won’t upload, media gallery does not display when adding post, lightbox bugged (and other tons of bugs)…
I first thought it was due to the new WordPress version, but that was not the problem. The problem is NextGen plugin (2.x).
Then I deleted nextgen and uploaded V1.9.3 .Website re-runs fast and stable.
I do not know what the problem is with the new version of NextGen (slow, unstable, buggy), but it seems to me that the problem is with Pope Framework…
‘ll use the old version as long as it works well. It did not even occur to me to install 2.x version…
Another bug:
Image upload not working. When adding a new post, pictures are not displayed from media. Solution: disable Nextgen plugin, add new post with image. Optimal solution: remove NextGen plugin because it’s very buggy and unstable or stick with V1.9.13.
EDIT: Just tested – I removed (deleted) the plugin (2.0.11) and upload 1.9.13.
It is a refreshing – fast, flexible, no bugs.A new version so ruined NextGen plugin, that this should be recorded in the history of wordpress plugin bugs. 🙂
Same problem. Infinite-Scroll removes all custom javascript…
Forum: Fixing WordPress
In reply to: UPM Polls-can't cats a voteSame problem here. It always show 0 votes. Tried to disable/enable jQuery but same result.
Is it possible to just make plugin to work without any other hacks?