Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Contributor photocrati

    (@photocrati)

    @davydov: A few thoughts here.

    First, just so you know, NextGEN 2.0 (just like 1.9.13) doesn’t fully support multisite. You should be able to activate on a multisite install, but you won’t be able to use it sub-blogs. So you should know that in advance.

    That said, you shouldn’t be getting an activation error. That error is similar we’ve seen to several generated by plugin conflicts, particularly BBPress and Magic Fields. Do you have either of those two plugins installed?

    Given that we’ve seen it on two other plugins, it’s quite possible that this is being generated by a plugin conflict. The only way to know for sure is to try deactivating all your plugins momentarily to see if you can activate NG. If so, it’s a conflict. If you do go through that process and find a conflict, please let us know.

    I also saw on another post that you were using different WordPress URL and Site URL under General options (ie, trying to install WP in yourdomain.com/wordpress but display it at yourdomain.com/). Are you doing that on this instance?

    Thread Starter davydov-denis

    (@davydov-denis)

    Pity you don’t support sharing media on multisite. That could make life of people who do multilingual blogs so much easier. Hope this feature will come in some future.

    I have none of the plugins you mentioned. I also tried deactivating plugins to see if it is a conflict, but it it not.

    p/s/ this is a fresh install, similar to another problem i reported recently. The one you mentioned is completely different site.

    p/p/s/ the problem is there for both 3.5.2 and 3.6

    Thread Starter davydov-denis

    (@davydov-denis)

    downgraded to 1.9.13, this problem is gone.
    Same plugins used. So it is definitely introduced in 2.0.0.

    Thread Starter davydov-denis

    (@davydov-denis)

    Going back to multisite support and shared media, it’s is actually rather simple and is described in this thread.

    I did the following:
    1. Create a gallery on the main site and put some images there.
    2. Turned off readonly for a gallery path in admin/settings.php
    3. Changed it so that it is the same as for the main site (blog_id =1).
    Instead of 2 and 3 one can do this as well.
    4. Changed table prefix for a DB in nggallery php so that it coincides with the one used for the main site, something like wp_ngg_pictures /…

    Now since databases are already created in the main (first) site, in all other sites it access the same DB and reads the same images. Seems to work fine.

    Al in all it is only about allowing users change DB prefix to something else so that one can use the same prefix for all Network. Should be pretty straight forward to add as an option (hopefully in version 2.1).

    Regards,
    Denis.

    Plugin Contributor photocrati

    (@photocrati)

    @denis: I’ll add this to our notes on multisite. There are actually quite a few things we need to do to get this working fully. Just so you know, it’s definitely hign on our priority list.

    Thread Starter davydov-denis

    (@davydov-denis)

    @photocrati

    thanks for your prompt reply. Happy to hear that this feature is on your to-do list.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Activation for a network fails (v2.0)’ is closed to new replies.