Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter MTWOFFICE

    (@mtwoffice)

    Tried if it will help to roll back, but also in v1.9.34 and 1.9.37 fooGallery refuse to work ??
    It looks like, the NextGen Gallery IS TO LARGE >1500 galleries with 80 to 400 pictures each.

    Thread Starter MTWOFFICE

    (@mtwoffice)

    Ok, finally found the problem: max_allowed_packet within the mysql config was too small, increased it to 500M and now foogallery is back working
    Maybe you can have a look into this, if you can free up some packages, when they are already moved from NextGen to Foo?
    Thomas

    Plugin Author bradvin

    (@bradvin)

    Thanks for reporting these issues @mtwoffice

    I have fixed the javascript console error and that will be in the next update.

    The max_allowed_packet config needs to be done on a server level, but it does not hurt in adding this to our documentation.

    thanks

    Looking forward to the update as this is causing foogallery to not load the galleries on the posts.

    Thread Starter MTWOFFICE

    (@mtwoffice)

    @bradvin

    You also have to delete the already imported NextGen Galleries and reset the Import than. It looks like the names of the old galleries are still within the MySQL Statement, which makes this problem.
    After you have deleted them it’s back working

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘FooGallery is not defined’ is closed to new replies.