beeeerock

@photocrati – Thanks Cais, the Reset Option didn’t solve the problem. I’ll fill in the Bug Report and request the Reset Tool, as it definitely is beginning to feel like there is a problem deeper down than can be accessed from the admin tools.

@photocrati OK Cais, I will put together a bug report. I’ll ask the site owners if they’re OK with providing credentials.

One last thing I’ve just noticed that might be relevant… and suggests a permissions problem to me…

Going into Gallery Options and Other Settings shows a pile of options… but I don’t seem to be able to make a change and have it stick. For example, ‘light box effects’ in Other Settings will let me select something other than the default ‘fancybox’, but pressing ‘save’ causes it to revert back to ‘fancybox’. Similarly, ‘nextgen basic thumbnails’ in Gallery Options has ‘0’ as the default for columns. Attempting to switch to something else and saving reverts back to 0. Save operations always show ‘save successful’, but the settings aren’t sticking.

I’ve read that uninstalling NextGEN pretty much breaks every bit of work done to albums, so I don’t want to do that… but it really seems like this problem may originate from deeper under the hood than the user interface lets me see…

@photocrati Thanks Cais, that makes sense to me and confirms I’m not too far off in my understanding. The only real issue we have here is the need to assign or create a page for each gallery in order to display the gallery’s thumbnails. That shouldn’t be necessary and is really what my problem boils down to. I think that’s the correct observation…

Is this something you think we can find a solution to, or am I best advised to simply accept the workaround of creating pages and forget about solving it?

@photocrati Thanks for bearing with me on this!

I’ve installed the latest (2.0.66.16) but things seem to work the same as described. Now I’m wondering if I’m expecting a behaviour that may simply not be part of NextGEN…

When a page with an Album appears, I think should see a thumbnail for each Gallery in the Album. Check. That works.

When I click on a Gallery thumbnail on the Album page, what should I get? Should I be sent to a page specific to that Gallery, with thumbnails of the Gallery images? Or should I get a popup slideshow (of some sort) of that gallery *without* a page change? I’ve been expecting the popup and have not been getting it, but perhaps that’s wrong??

@photocrati Further to my previous post, what I meant to say is that I was of the understanding that the galleries could exist and be viewed *without* a dedicated page for each gallery being created. If that’s not the case – and I DO need to have a page created for each – I may have found the solution.

But I suspect I shouldn’t have to do it this way…?

Yes, what you see on the gallery page is the latest attempt to get it to function.

Looking in the gallery settings for the last person on the current list (Bob) I see that the ‘gallery path’ in the gallery settings points to: wp-content/gallery/bob-hubbard. I see that the link on the actual viewable page points to gallery/nggallery/bob-hubbard. I realize they may not fully correlate but wonder if the radical change in versions of NextGEN may have changed some of the internal directory structures or aliases?

While messing about just now I’ve found a few things that may be important, or may simply show I really don’t know what I’m doing with this plug-in…

1) Looking in the Gallery Editor for a specific gallery (in this case, Bob’s) I note that ‘Link to Page’ shows ‘not linked’.

2) Still in the editor, ‘Create new page’ says ‘Main Page (no parent)’

3) If I click the button below that ‘Add Page’, the ‘Link to Page’ now shows the gallery name and a page of that name is created. The link on the Gallery page works, with the gallery appearing on its own page.

However, I think we’re looking for the gallery to appear floating above the gallery page, aren’t we, in a viewer? Perhaps this helps point at the area to check?

Hi Cais,

Thank you for your reply!

The site is at https://www.kamloopsphotoarts.ca/ and of course, the gallery page is at https://www.kamloopsphotoarts.ca/gallery/

The site is skinned with the 2014 theme while we work through the problems, hence it may not look like it should. At this time, the only plugin activated is Nextgen Gallery.

Thanks in advance!

Cais,

I reset the gallery and cleared the cache. The result was that clicking any of the galleries in the album that showed on the page caused a quick flash on the browser of something that can’t be seen (too fast), before showing the original page again.

I then tried something other than ‘defaults’ for the permalinks. No difference – still the quick flash and back to where I am.

Tried the 2014 theme. Again, same behaviour. No other plugins active.

So this is different to what I had – something happens besides the spinning spinner… but still not right.

I’m not anxious to do all the reinstallation – I don’t know how they’ve got this site hosted, but I’m going to bet that I won’t be able to get root access to the server, which is the only way I’ve worked with WordPress installs in the past.

The visual editor now lets me insert the album in a way that looks correct. No triangle exclamation mark.

Suggestions as to what I should try next? Thanks!

Hmmm. That’s an interesting solution. I’m pretty sure I created a site or two along the way that was deleted… it was my first multi-site installation so everything took place on the learning curve. My initial response to your post was that my problem didn’t happen the first time there was an update. But I may not have deleted a site yet.

If this is in fact the cause, I wonder if this should be considered a bug? I think it is by my definition. Have you reported your findings on the bugs page?

I will look further into this as time allows and perhaps you’ve found the solution to my problem. Thank you or posting your experience – certainly not seen as hijacking!!! ??

Done.

I backed up .htaccess and deleted all the stuff between the iThemes tags (there was plenty of it).

I was worried that some basic settings might have been included between the tags that would have been ‘returned’ to htaccess with a clean uninstall of the plug-in. However, so far no apparent concerns, so I’m going to assume the deletion hasn’t broken anything else.

No response, so I’ve been poking around when I have a few minutes. And, I think I’ve solved this.

I added the private IP and URL to the ‘hosts’ file. This now allows the ‘update sites’ command to execute properly. And looking in the database, I can see that the db_version has been incremented properly now.

So it would appear that some of my assumptions were wrong:

– upgrading the WordPress version does not seem to increment the db_version, but the ‘update sites’ command evidently does.
– the ‘update sites’ process requires the server to be able to access itself by URL, rather than simply edit the database directly.
– the ‘update sites’ starts with the last site added, not the first as I had assumed.

Perhaps there is more going on than I’m seeing, but from how I *apparently* solved this problem it would appear that my observations are correct. None makes much sense to me though…!

I’ll give that a try… thanks!

Still wish the problem could be solved to avoid manually adjusting this parameter though…!

Hmmm. That link doesn’t show the 22442 version that fixed the problem last time – which makes me wonder if this list is complete. Maybe I’m best to check another site and use whatever number it shows.

But it would be nice to know why the problem is recurring so as to fix it once and for all!

Same problem after the upgrade to 3.6 today!!! ??

Assuming I need to go about fixing the problem in the same way, how do I know what the db version value should be now? 22443?

There is obviously a reason why this is happening… it would be nice to be able to do upgrades without mucking about in the database!