Forum Replies Created

Viewing 14 replies - 16 through 29 (of 29 total)
  • Yup, same here after upgrading to 11.7.

    Foutdetails
    ===========
    Een fout van het type E_ERROR werd veroorzaakt op regelnummer 22 van het bestand /www/wpss/wp-content/plugins/wordpress-seo/vendor/composer/autoload_real.php. Foutmelding: Uncaught LogicException: Passed array does not specify an existing static method (class 'ComposerAutoloaderInitf21b8825991ccda35c7813f5b3928f77' not found) in /www/wpss/wp-content/plugins/wordpress-seo/vendor/composer/autoload_real.php:22
    Stack trace:
    #0 /www/wpss/wp-content/plugins/wordpress-seo/vendor/composer/autoload_real.php(22): spl_autoload_register(Array, true, true)
    #1 /www/wpss/wp-content/plugins/wordpress-seo/vendor/autoload.php(7): ComposerAutoloaderInitf21b8825991ccda35c7813f5b3928f77::getLoader()
    #2 /www/wpss/wp-content/plugins/wordpress-seo/wp-seo-main.php(79): require('/www/wpss/wp-co...')
    #3 /www/wpss/wp-content/plugins/wordpress-seo/wp-seo.php(48): require_once('/www/wpss/wp-co...')
    #4 /www/wpss/wp-settings.php(362): include_once('/www/wpss/wp-co...')
    #5 /www/wpss/wp-config.php(93): require_once('/www/wpss/wp-se...')
    #6 /www/wpss/wp-load.php(37): require_once('/www/wpss/wp-co...')
    #7 /www/wpss/wp-admin/admin-ajax.php(22): require_once('/www/wpss/wp-lo...')
    #8 {main}
      thrown

    After removing the wordpress-seo folder via FTP, the error displayed when visiting the website changed to.

    Fatal error: Uncaught InvalidArgumentException: A service provider must be a fully qualified class name or instance of (\League\Container\ServiceProvider\ServiceProviderInterface) in /www/wpss/wp-content/plugins/rocket-lazy-load/vendor/league/container/src/ServiceProvider/ServiceProviderAggregate.php:47 Stack trace: #0 /www/wpss/wp-content/plugins/rocket-lazy-load/vendor/league/container/src/Container.php(171): League\Container\ServiceProvider\ServiceProviderAggregate->add('RocketLayyLoadP...') #1 /www/wpss/wp-content/plugins/rocket-lazy-load/src/Plugin.php(81): League\Container\Container->addServiceProvider('RocketLayyLoadP...') #2 /www/wpss/wp-includes/class-wp-hook.php(286): RocketLazyLoadPlugin\Plugin->load('') #3 /www/wpss/wp-includes/class-wp-hook.php(310): WP_Hook->apply_filters(NULL, Array) #4 /www/wpss/wp-includes/plugin.php(465): WP_Hook->do_action(Array) #5 /www/wpss/wp-settings.php(394): do_action('plugins_loaded') #6 /www/wpss/wp-config.php(93): require_once('/www/wpss/wp-se...') #7 /www/wpss/wp-load.php(37): in /www/wpss/wp-content/plugins/rocket-lazy-load/vendor/league/container/src/ServiceProvider/ServiceProviderAggregate.php on line 47

    After entering recovery mode I disabled Lazy Load by WP Rocket. Purged all caches in W3 Total Cache. And things were back to normal.

    Enabled Lazy Load by WP Rocket. Cleared caches again. Still good.

    Reinstalled Yoast SEO. Cleared caches again. Still good.

    Hope the team can figure out what went wrong and avoid it in the future.

    Thank you for creating and maintaining this free plugin!

    • This reply was modified 5 years, 4 months ago by tfmwa.
    • This reply was modified 5 years, 4 months ago by tfmwa.
    Thread Starter tfmwa

    (@tfmwa)

    And thank you for creating and maintaining the plugin! ??

    Manual is always an option. But when you’re dealing with a large site that has thousands of pages with hundres of redirections over the years… not so much.

    I don’t know if it’s possible, but maybe in the future AMP for WP could be expanded to detect any redirects on the canonical version of the page and follow the same redirect on the AMP version. Or simply not create an AMP version in that case.

    When editing your table, scroll down until you see the Pagination checkmark and change the number associated with it.

    Thread Starter tfmwa

    (@tfmwa)

    Great to hear about the update notifications.

    And thank you very much for providing the sample code to create a filter that automatically applies responsive/scroll to all tables. It works like a charm.

    I hope this can help others as well. ??

    Hi Scott,

    Thanks for creating and maintaining this awesome plugin.

    Currently in version 1.3.3 the saved Destination URL will not be processed when generating static files and the resulting static files still contain the Origin URL.

    Also, the Last Updated date for this plugin on the WordPress site is 1 minute ago but inside the WordPress Dashboard Last Updated it’s 46 years. ??

    Thanks for posting the solution. I had the exact same issue.

    Simply unchecking “Use Lightbox for YouTube- and Vimeo links” under Responsive Lightbox’s options will do the trick.

    Probably a little late for OP, but maybe it will help someone else.

    To get the gallery overview images centered, add this to the plugin’s Advanced Settings/custom css:

    div.afg-cell {
    text-align: center;
    }

    This issue has resurfaced with WP 4.0 and Flickr Photostream 3.1.6.
    Showing the full photostream works. Trying to show a specific tag results in “No photos”.

    The fix provided by @terryfinney still works, thank you! Hopefully this can updated in the plugin once again.

    Thank you for creating it. It’s a wonderful and straightforward way to display the photostream on a WordPress site.

    Thank you so much for sharing the solution, kiwiot!

    Maybe an added tip for anyone struggling with sharing images from Flickr to WordPress: when you’re on a photo page, on the bottom left there is either an Optin to the new experience or an Opt-out and Feedback button.

    Sharing to WordPress is known to NOT work when the new photo experience is active. Until they fix that, opt out of the new experience and the share to WordPress feature should work again.

    After that, you can use kiwiot’s fix combined with this plugin to have thumbnails automatically generated for Flickr images that you post to WordPress from Flickr.com.

    The size of your thumbnails in WordPress can be defined under Dashboard > Settings > Media.

    tfmwa

    (@tfmwa)

    Yeah I think there’s still an issue when you want to use the same slug at the beginning of the url for both a category and a product in Woocommerce.

    /shop/shoes/ = fine
    /shop/shoes/converse-all-stars = 404 error for product page
    and even
    /shop/converse-all-stars = 404 error for product page

    This is basically the 4th provided Woocommerce Permalinks option:
    /shop/product-category/sample-product/ (my store page is Shop)
    or
    /shop/%product_cat%

    So you’d expect it to be possible to do this as it’s a suggested option.

    If you use the default setting or different names for the first slug in the url path, it seems to work just fine.

    It took me a while to accept ‘shop’ as a virtually must have part of the url. I’m not quite yet willing to budge on not having my product urls be an extension of a category url.

    tfmwa

    (@tfmwa)

    I’m trying to accomplish the same structure as user Portoa and this still seems to be an issue.

    /shop/ as a base shop page = working
    /shop/category/ for a category = working
    /shop/category/product for a product = 404

    I’ve tried several suggested solutions found here and on developer sites, but so far I have not had any luck with them.

    Does anyone have a recent fix that works? Thanks in advance for taking the time to reply.

    WordPress 3.7.1–nl_NL
    CANVAS 5.5.3
    FRAMEWORK 5.5.5
    Using a custom child theme (which is just an empty stylesheet) because it’s recommended.

    I can also confirm that the issue is not present in 9.2.11 and that a rollback helped to fix it in our case.

    Hopefully the plugin owners can look into this as soon as possible.

    Thread Starter tfmwa

    (@tfmwa)

    Hi cartpauj,

    Thanks for your reply and for considering this suggestion.

    I know where you’re coming from. I’ve suggested the same thing to the product owner (to change it) and the affiliate network (to not allow special characters).

    Thanks for your suggestion to work around the issue. I’ll give it a go!

    @urkekg
    Thank you SO much for posting the replacement code. It worked great on my site.

    It would be awesome if this issue could be resolved within the plugin. I love Display Widgets, but not being able to disable these options once they’ve been enabled can be quite troublesome.

    Unticking the box and saving the widget just causes the checkbox to become checked again at the moment.

Viewing 14 replies - 16 through 29 (of 29 total)