VesaT

@cais, could be something in web hosting, even though “Default” does not seem to work at two different local test platforms either (AMMPS and Wampserver) on Windows 10, and occasionally also XAMPP on Mac/OS X.

For on-line web sites I use one single hosting company who also provide linux-based WordPress environments as a service. I always have installed WP personally there, as it is so easy ?? All other sites but my personal site have been using “Post Name” setting in WP.

If it helps you think about why those errors with WP default setting of permalinks in any way: NGG shows this host currently running PHP 5.4.45 and MySQL 5.5.48-cll, so should be about uptodate.

@cais – thanks a lot again! Your suggestion to use “post name” as WP permalink structure seems to solve this, and all albums I’ve tested so far show galleries as planned.

But, I still think NGG should also work on WP permalink default setting ?? Maybe you can have a look at that sometime.

@photocrati – Cais, first: thanks for the check of a linked gallery; at my testpage the older gallery was (automatically By NGG at the creation time!) linked to the FrontPage. When I removed the link from the old gallery, this album now shows both two galleries perfectly – like NGG should ??

But, on my live personal site, have a look e.g. at this page:

This page is very simple, using several albums, which contain one to six galleries each. The galleries very uploaded in August 2012 and I haven’t touched the page since. None of will show from any of these albums, the result is just an error message 404 (not even on my site’s 404-page!). If you hover over any gallery (none them linked to any page), the URL you see is like this one:
https://www.tiirikainen.fi/wordpress/nggallery/city-of-helsinki/helsinki-city-summer-shots?page_id=1677 – and this does not show.
When I switched a local test copy of this site to use NGG 1.9.13, the URL shown is very different – and it works:
https://localhost/wordpress/?page_id=1677&album=17&gallery=76

Page content here in text mode for reference, just text and shortcodes is as follows:

Some time ago I moved all my photos from Facebook into these galleries, with English captions. Main reason for doing so are some copyright issues that I’m not fond with in Facebook.

Currently the following albums contain photos with English texts:

[album id=16 template=compact]
<hr />
[album id=17 template=compact]
<hr />
[album id=18 template=compact]
<hr />
[album id=19 template=compact]
<hr />
[album id=20 template=compact]

@photocrati – the problem here is that “test gallery” is a normal gallery within an album and should show up as gallery thumbnail It has been uploaded about two yearsago with and o?d NGG. It is NOT linked to any page, shoud show up pn the same page, and showed up pk only a short time ago.
Looks like NGG 2.1.46 is generating some odd linking code. On my personal site wwww.tiirikainen.fi all galleries uploaded some time ago and shown through albums end up in an error 404, not even showing my error page. See the first post in this thread.

@photocrati – Cais, I still see the same result. If you go to the NGG album testpage using that link, click first the “0ld” gallery labeled “test gallery” (result is the same regardless of whether you click the above album displayed with classic NGG shortcode or the newer NGG media insert album / test gallery) and at least for me on a couple of browsers and using Windows 10 Computers the system reverts to the front page. But if you click on the second gallery labeled “test gallery for albums” (created using NGG 2.1.46 just a day or two ago), the gallery shows up as it should – both on the shortcode display (above) or NGG media insert (below).
The resúlt seems to be the same when looking at the test page in my Android phone.

A bit of more info. I tried NextGEN Gallery Reset plugin at my testsite, but no help. Albums only show new galleries made with NGG 2.1.46, possibly also some that are a bit older.

A bit more information, based on tests with a local copy of my personal site https://www.tiirikainen.fi – and also the live site. Hope these help to solve this puzzle.

Both my local copy of the site and the live site always seem to end up not showing any galleries included in the album, and regardless of whether the page tries to show them with a classic NGG shortcode like [album id=23 template=”extend”]. The page shows the gallery summaries, but not the actual gallery contents ie. images. What the browser shows is a message:
“Not Found

The requested URL /wordpress/nggallery/elamaa-palm-springsissa/anza-borrego-desert-state-parkissa was not found on this server.

Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.”. The URL is excactly like this: https://www.tiirikainen.fi/wordpress/nggallery/elamaa-palm-springsissa/anza-borrego-desert-state-parkissa?page_id=8857

I do not know if it helps you in any way, but for information:
If I switch from NextGEN Gallery to NextCellent Gallery (the fork of NGG 1.9.13) the classic shortcodes work perfectly. I have this plugin at my local site for testing, but the database and …/gallery folder area few days old copies of the live site.

I do not wish to switch permanently into NextCellent Gallery as it lacks many features of current NGG and does not work with NGG Pro whose display styles is use a lot. I would also need to go through al my few hundred posts and pages to guarantee some kind of display of images ??

Hi Responsive Menu,
at my local test environment – which I’m running on top of AMPPS and using PHP 5.3 because of a very versatile theme development tool requiring it.

When I updated Responsive Menu to the newest 3.0.5 version, a parse error appeared and neither the admin side of WP nor the test site itself did not work at all. Then I deleted Responsive Menu and reinstalled it as a totally new plugin and it did not activate but displayed a text telling “could not activate the plugin as it caused an error”. Now the local test side works fine – but without Responsive Menu. But obviously Responsive Menu installation works as it should, preventing a parse error and closure of the site in total.

Looks like I need to find a way to run two local environments – one with PHP 5.3. and another with the newest PHP versions.

Hi,
I have also faced some issues with WP 4.5.3 and NGG 2.1.46. Admin part seems to work without problems, as well as different displays (classic thumbnails, imagebrowser, Pro blog style etc.)of galleries work ok.

But I have now problems with displaying galleries through albums, the result is in most cases just 404 (not found) but occasionally displays correctly. So far I have not found any clue why this happens, even though it seems to raise only on pages, but not any posts. Another plugin and conflict with NGG could be the source, but I tend to think there is some transient conflict with WP 4.5.3 and NGG when handling pages.

Previously all albums displayed galleries as it should in thumbnails whether the galleries were new or several years old. I found the problems accidentally when trying to find an few years old image which belongs to a certain album. Possibly this has also something to do with the number of images and galleries, my site has more than 3 000 images in almost 200 galleries.

I’ll keep on testing and hope to find a solution or workaround soonest. Sometimes it seems a workaround that works is to build a (static) page anew from scratch and use NGG media insert to display albums – but even this does not seem to work with all albums/galleries. As said all albums and galleries show up correctly at admin side.

A manual downgrade is shown in the second message of this thread. I have done as said, and the site works now fine.

And I will not upgrade to new a version before it has full backwards compatibility, including CAPTCHA codes. Currently I have no time playing with special fields of the newest version which is otherwise backwards compatible I presume.

I’m managing a website for a business with hundreds of daily users and today automatically updated Custom Contact Forms to the new version. So no contact forms available before I revert back to previous version.

What the new version should at least have is a warning that contact forms from previous version will not work! I started wondering why there are no new contacts at the admin side and realized the new version does not support old shortcodes – which should also be an option, like in most totally rewamped plugins. Before that comes around, I’ll stick to the old version or change to another contact form -only plugin.

Hi, I just downloaded Beta 3 and copied it to one of my test environments running NextCellent.

It seems to work alright in all other aspects but on WP admin screen the prompt to upgrade database gives a message “You do not have rigths to do this” (or something like that as this site/NextCellent runs on Finnish).

Upgrade within NextCellent admin screen worked fine.

@niknetniko: I fully understand your statement, being one of the contributors to NextCellent as a translator.
I also know very well the status of NGG as Alex Rabe left it: working, and working well, but code is what you get after years of development as a single “hobbyist” if you like. It is clear that for larger future functions some reverse engineering is needed to get it all working.

But, the fact is that current NGG 2.0.69 works pretty well without any paid extra plugins and has gained a lot of new users. If NextCellent (being a fork of NGG) will not get the problems away pretty soon, many users may abandon this great effort of WPGetReady and yourself. That would really be a shame as there are still features in NextCellent that NGG’s latest versions do not have (e.g. Imagebrowser with EXIF data, rotation of images working in all environments…).

Hope you guys find soon some solutions (and time) to fix what needs to be fixed as there are most possibly not many others who would have time to dig into the code and make it better.

Well, I agree mostly, but also want to remind that:
– NextCellent Gallery only exists because NGG after upgrading the whole architecture into a new “better” one had serious problems to get the previously very solid and bug-free plugin a mess with lots of bugs.
– NGG as such is a free plugin like NextCellent; from the users’ perspective what counts is how well the plugin works. I maintain some sites using the Basic NGG 2.0.xx currently without any real problems.

I also think some of the recent NextCellent bugs are somewhat related to the same problem NGG 2.0 faced: broadening functionality while at the same time “cleaning” the very well working code – maybe because of WordPress development. If I’m totally wrong here I would like the plugin developers correct me. Running an old plugin version due to any bugs in more recent releases is not ok.

There are currently several php files controlling imagebrowser functionality in this folder and its subfolders:
…/wp-content/plugins/nextgen-gallery/products/photocrati_nextgen/modules/nextgen_basic_imagebrowser/. Just looking at those files clearly shows how different e.g. getting certain image-related field values from your WP database are in NGG now and prior to 2.0 release.

There is one php file managing basic imagebrowser functions named netxgen_basic_imagebrowser.php in the /templates subfolder of the above mentioned module folder.