Forum Replies Created

Viewing 15 replies - 316 through 330 (of 384 total)
  • Rebuilding depends on you or how deep your pockets are. Easy solution of course is to pay someone to do what is desired.

    With that said, doing it yourself depends on how much you know and … how much you know you don’t know. If you know about basic site security and how to troubleshoot problems and how to know if a Plugin is good or bad then have at’er. If you know there is a lot you don’t know about those things then are you willing to spend the time learning; and how long will it take.

    Also, was the previous person a whiz at this stuff or did they do a lot of things they shouldn’t have–and nobody knows about?

    Not being able to see the site or know what you want to accomplish, I can only give you ideas as to what to do.

    When debug is enabled in the wp-config:

    define(‘WP_DEBUG’, false); change to define(‘WP_DEBUG’, true);

    You’ll find error logs in these locations:
    /public_html/error_log
    /wp-admin/error_log

    Also have a look at this Article:

    Debugging in WordPress

    public_html/error_log
    public_html/wp-admin/error_log

    First thing to do is determine what Plugins are necessary or desired. Researching each one will help you to better understand about Plugins and which ones you want. Will also help when choosing a Plugin in the future.

    Then determine if the current Theme is desired or …? That will help in determining if a website makeover is viable now or down the road.

    This doesn’t take away from the fact that one should always be aware of basic site security and maintenance, regardless of WordPress site or not.

    My recommendation is to focus on Security and Backup Plugins. WordFence and Updraft come to mind as good ones to start with. Also make sure everything works with PHP v7.3 and get rid of whatever doesn’t.

    That should keep you busy for a few days. 😉

    Getting same error with WP 5.5 and WooCommerce 4.4.0.

    [18-Aug-2020 18:44:42 UTC] PHP Fatal error: Declaration of Automattic\WooCommerce\Internal\DependencyManagement\ExtendedContainer::get($id, bool $new = false) must be compatible with League\Container\Container::get($alias, array $args = Array) in /wp-content/plugins/woocommerce/src/Internal/DependencyManagement/ExtendedContainer.php on line 18

    Also noticed this in download results:

    The authenticity of woocommerce.4.4.0.zip could not be verified as no signature was found.

    You could use the DevTools built into your Browser. If not sure how then use a Search Engine to find tutorials specific to your Browser.

    You could also use a plugin like this to help troubleshooting back-end or front-end problems.

    https://wordpress.org/plugins/query-monitor/
    Query Monitor By John Blackbourn

    I use it all the time and it can be really helpful.

    Here is a plugin I’ve worked with a does as advertized.

    https://wordpress.org/plugins/media-library-plus/
    WordPress Media Library Folders by Max Foundry

    If not to your liking then search the plugins for “media library” to see others.

    You can confirm that by disabling the lazy load enabled by 5.5

    https://wordpress.org/plugins/disable-lazy-loading/
    Disable Lazy Loading

    Does one thing: disables WP Lazy Load feature enabled in v5.5.

    Install this Plugin and see if it helps.

    https://wordpress.org/plugins/enable-jquery-migrate-helper/
    Enable jQuery Migrate Helper

    Also make sure to install a Backup Plugin if you haven’t already.

    I think we can all agree that v5.5 has some issues and we either use something else or fix what we have.

    Feel free to post other problems you are having, either here or in a new thread, or you can mark this thread as Resolved.

    It’s good to hear you were able to sort out your problem.

    Please mark this thread as Resolved.

    Have your Hoster downgrade your PHP to v5.6 which I presume you were using before and everything was working fine. Then update WordPress to v5.5 and immediately install this plugin:

    https://wordpress.org/plugins/enable-jquery-migrate-helper/
    Enable jQuery Migrate Helper

    Then update Themes, check a few things on your site to make sure all is good.
    Then update Plugins and check again.

    Then do a backup. Then ask your Hoster to upgrade your site to PHP v7.3. I know v7.4 is the latest but v7.3 is just fine for now.

    I know it a lot a of steps but but the above should get you to where you want to be.

    Thread Starter Website Rob

    (@website-rob)

    “Enable jQuery Migrate Helper”

    The Starter Sites plugin displays msg. in page, as shown in the image.

    The One Click Importer plugin also shows the same msg. in page.

    Browser Console shows 4 warnings.

    
    This page uses the non standard property “zoom”. Consider using calc() in the relevant property values, or using “transform” along with “transform-origin: 0 0”.
    - themes.php
    
    JQMIGRATE: Migrate is installed with logging active, version 1.4.1 jquery-migrate-1.4.1-wp.js:23:17
    
    Layout was forced before the page was fully loaded. If stylesheets are not yet loaded this may cause a flash of unstyled content.
    - jquery.js:3:25903
    
    This site appears to use a scroll-linked positioning effect. This may not work well with asynchronous panning; see https://developer.mozilla.org/docs/Mozilla/Performance/ScrollLinkedEffects for further details and to join the discussion on related tools and features!
     - themes.php
    

    “Test jQuery Updates”

    No msg. on either plugin page.

    Browser Console shows the first 3 notices as above whilst the 4th one is not.

    (this not shown)

    This site appears to use a scroll-linked positioning effect. This may not work well with asynchronous panning; see https://developer.mozilla.org/docs/Mozilla/Performance/ScrollLinkedEffects for further details and to join the discussion on related tools and features!
     - themes.php
    

    So it would seem that for whatever reason, the “Enable jQuery Migrate Helper” states in page that there is an error but not what and will be confusing to most. If one is familiar with using a Browser Console to look for errors then there is no need to display an uncompleted error msg. in page. Although in page is a “touch of class” for a complete msg.

    Looks like it’s time to decide which way to go with error display and do a bit of tweaking. 🙂

    Install this Plugin and see if it helps.

    https://wordpress.org/plugins/enable-jquery-migrate-helper/
    Enable jQuery Migrate Helper

    Also make sure to install a Backup Plugin if you haven’t already.

    Did you perhaps skip over a few things you did? Your problem is with the version of PHP being used which is not working correctly with old Plugins. If you want to solve your problem go back to PHP v5.6 and do some WordPress Updates.

    Mostly likely everything will work again after the updates and more importantly, the site will work correctly. Then you can upgrade PHP and any problems you do have will be a lot easier to sort out.

    If you don’t want to downgrade PHP then delete the site and start over.

    A bit of confusion here as the “Skip to Content” link only shows when using the Tab button on the keyboard. I do not see it otherwise.

    This is one line of HTML that has been inserted into all your pages, in the BODY code. This is a nice touch actually as it meets with Accessibility Guidelines. It provides for those using Screen Readers to avoid having to always listen to the Header info & links being read out to them and jump right to the content.

    How is this a “problem”?

Viewing 15 replies - 316 through 330 (of 384 total)