uwebhofer
Forum Replies Created
-
Spencer, thanks for the quick reply. I checked and it says version was 2.9.8.10! I do have a screenshot of it but not sure how I can add it here to show you. So I deleted the app and reinstalled it and it’s now 2.9.8.4 and I was able to connect it. FUNKY!!!
Thanks @bradvin for being so responsive! It still doesn’t really explain why it worked until about few weeks ago since it is a customized theme that hasn’t been updated in a year or two. I believe the solution will be to hire a programmer to look at the code in total and make sure the theme is up to date. Foundationpress uses Sass, so maybe that’s the issue.
Just FYI, this is the entire functions.php code.<?php
/**
* Author: Ole Fredrik Lie
* URL: http://olefredrik.com
*
* FoundationPress functions and definitions
*
* Set up the theme and provides some helper functions, which are used in the
* theme as custom template tags. Others are attached to action and filter
* hooks in WordPress to change core functionality.
*
* @link https://codex.ww.wp.xz.cn/Theme_Development
* @package WordPress
* @subpackage FoundationPress
* @since FoundationPress 1.0.0
*//** Various clean up functions */
require_once( ‘library/cleanup.php’ );/** Required for Foundation to work properly */
require_once( ‘library/foundation.php’ );/** Register all navigation menus */
require_once( ‘library/navigation.php’ );/** Add menu walkers for top-bar and off-canvas */
require_once( ‘library/menu-walkers.php’ );/** Create widget areas in sidebar and footer */
require_once( ‘library/widget-areas.php’ );/** Return entry meta information for posts */
require_once( ‘library/entry-meta.php’ );/** Enqueue scripts */
require_once( ‘library/enqueue-scripts.php’ );/** Add theme support */
require_once( ‘library/theme-support.php’ );/** Add Nav Options to Customer */
require_once( ‘library/custom-nav.php’ );/** Change WP’s sticky post class */
require_once( ‘library/sticky-posts.php’ );/** If your site requires protocol relative url’s for theme assets, uncomment the line below */
// require_once( ‘library/protocol-relative-theme-assets.php’ );?>
With all plugins deactivated except the two FooGallery plugins (regular and foobox lightbox) and the two SiteOrigin (regluar and widget bundle) nothing changes. But with a default theme enabled it works! Ta da! It’s a custom theme built for the website when I wasn’t involved. So it looks like it’s not an issue that you can fix with FooGallery. On the other hand… it used to work and there wasn’t any theme update since at least 2 years. So it either got broken with one of the last Foogallery updates or a wordpress update.
- This reply was modified 8 years, 3 months ago by uwebhofer.
I did deselect automatically add paraphgraphs, but no changes. I also tested this on a new page: http://risers4rett.org/testing-foogallery/ – with three versions: 1. FooGallery widget through siteorigin, 2. FooGallery code [foogallery id=”550″] and 3. gallery through media insert. Only 3. works.
As a backup plan, and for grins and giggles, I added a the FooGallery code to a new page without using the page builder function and it works: http://risers4rett.org/testing-foogallery-w-o-page-builder/I guess for the time being I can use the backup plan, but that doesn’t solve the functionality issue between the two plugins… Thoughts?
I turned off lazy loading for each of the galleries on that page and also tried in the general settings – with cleared cache – no changes 🙁