NextGen and Multisite Issue

I see the same thing on multisite. I have an 85 sites multisite network running NetxGen 1.9.13. Been running NextGen on it for over 2 years starting at version 1.7.x I think with no issues.

I recently tested the update to 2.0.0 and to 2.0.7 on a dev copy of the site and I see the same issue as laskowv. No matter what site I’m on in the network, if I try to insert a gallery in a page or post from the NextGen button it only shows me the galleries from the main site, not the actual site I’m on.

Also, it may also be multisite related as I didn’t get that issue updating a regular standalone site but, if I go to the Gallery Settings page, none of the options labels are displaying. Many of the actual options are empty too.

If I do an options reset in Other Options, the options labels show but, I would have to go through 80+ sites on the network to reset options then redo the settings the way they were before… in the new system which is completely different than the old (which was SOOOO much easier to use with tabs than it is now).

So basically, I’m stuck at 1.9.13 until you can make it work correctly on multisite again or I find an alternative. I was going to go Pro with all the new features and thumbails pagination now works with any lightbox option which I’ve waited on since I started to use NextGen. But the broken state of this update does not instill confidence and load time on pages with galleries seems much slower than before too.

Thanks

pixelyzed … here’s what I have learned so far.

I also rolled back to 1.9.13. FTP’d and removed all of the galleries from the blog directories from each (ex: blog.2.dir->files). Reset the Network Settings and changed the path to be wp-content/gallery for ALL sites, including subsites.

All sites can see their own galleries. Tested another theory; had a gallery (call it trees) on subsite that I wanted to duplicate on main site with same name. Used “import folder” option on main site to import the “trees” gallery on main site. It imported it and gave it a new gallery id on main site and nothing was harmed on the physical folder (most probably overwrote it).

Now, what I did find is that I have a galleryid = 17 in main site with and a galleryid = 5 on the subsite. ALL sites still have wp-content/gallery as their path. RESULTS: the gallery databases for each site are registering each gallery and giving them new id’s — regardless of the path.

What this proves is that all versions are not correctly following the directory path settings when it comes to “inserting into the post”. I have seen a few corrections to code variables posted in this support area that might be the solution for multisites to work correctly. Maybe the developers should try these out?

laskowv

Thanks for the heads up on this fix although, with a network as large as this, it would take a while to do the change. I’ll test this out though.

But I would appreciate if someone from Photocrati could post here and tell us if they are aware of this issue. I tested the update on 4 multisite installs that worked fine beofre and that show this problem after update: intserting a gallery from sub site shows only the main site’s galleries although the path setting is wp-content/blogs.dir/%BLOG_ID%/files/ as always.

Thanks

@laskowv, @pixelyzed: I just want to confirm that 2.0 is not fully multisite compatible and will cause issue on sub-blogs. Actually, I’m surprised you’ve had the Legacy version working, since that one actually also tends to cause issues on multisite. We’ve been aware of that from Legacy onward, and it’s very high priority once we get through the current slate of issues from the upgrade.

For now, if you have it working with 1.9.x, you should definitely just hold there until you see explicit confirmation that 2.x is now fully multisite compatible.

photocrati, this should be a very simple fix for you guys…..

Obviously, the app that is executed within a page/post is looking at the path defined in the options for single sites. On multisites, the full path is also defined for those sites, but the full path is not being referenced — it is just using the standard wp-content/gallery. The code needs to be changed to include the database or path variable as the prefix; this will fix it. I found another posting where they had modified theirs and posted in one of these threads. Of course, an update will wipe it all out again. (I think it was either $path or $dbase; something like that).

My “fix” was to change the path to all of my multisites to be the same as the parent site; however it all depended on whether or not the plugin on each site wrote a valid record in it’s on nextgen database — which I have proved that it does. If it had not, then I stood the chance of corrupting another gallery that would have an identitcal ID as the other site.

I do not currently have as many multisites as others, but soon will.
Thanks

laskowv, help them do it ??

I will send you a bag of apples!

@laskowv

With your fix to move all galleries to a single wp-content/gallery, do users see all the galleries in there or just their own? If they see all galleries, this solution is not workable for me. I need each site and user access isolated from one another. And you’d imagine that with 85 sites on the network, if users see everyone’s galleries, it would get very confusing very fast for them.

For now I’m just waiting for Photocrati to make NetxGen multisite compatible or at least get it to the state 1.9.13 was before I upgrade. The UI changes will cause me enough trouble with users that I don’t want to complicate things any further for them.

Thanks!