Forum Replies Created

Viewing 9 replies - 1 through 9 (of 9 total)
  • Thread Starter fwade

    (@fwade)

    Thanks for that link.

    I suspect that the culprit was the way I used Updraft – it didn’t recognize the first site and overwrote the images in the multisite.

    I’m looking to see why it would do that so that it never happens in future.

    Same happened here as my provider hasn’t upgraded the php version.

    How can I download version 7.13.3?

    Thread Starter fwade

    (@fwade)

    I think it’s fixed. Rather than use the prior update, I did an auto-update to WP 4.9.7 within WP and the problem went away.

    Thread Starter fwade

    (@fwade)

    I may also add that this entire problem started when I tried to update a plugin. It crashed my site and took the entire wp-includes folder with it.

    It forced me to restore WordPress manually, which fixed the problem but introduced the new problem I noted at the top of this thread.

    Apparently the plugin required PHP 7 and my site uses PHP 5.4 – this might explain the original issue, but not necessarily the latest.

    As I read other threads I believe that the only common denominator is the latest WP update. As a result, I’m going to roll back to a prior version of WP manually and see if that works. Other WP sites on my hosting are working with WP 4.9.7 so I don’t believe this is a site issue.

    I welcome any help.

    Thread Starter fwade

    (@fwade)

    All kinds of errors… BTW, the same problem occurs on Firefox.

    Chrome –

    JQMIGRATE: Migrate is installed, version 1.4.1
    core.min.js:1 Failed to load resource: the server responded with a status of 404 (Not Found)
    widget.min.js:1 Failed to load resource: the server responded with a status of 404 (Not Found)
    mouse.min.js:1 Failed to load resource: the server responded with a status of 404 (Not Found)
    suggest.min.js:1 Failed to load resource: the server responded with a status of 404 (Not Found)
    autocomplete.min.js:1 Failed to load resource: the server responded with a status of 404 (Not Found)
    menu.min.js:1 Failed to load resource: the server responded with a status of 404 (Not Found)
    sortable.min.js:1 Failed to load resource: the server responded with a status of 404 (Not Found)
    core.min.js:1 Failed to load resource: the server responded with a status of 404 (Not Found)
    widget.min.js:1 Failed to load resource: the server responded with a status of 404 (Not Found)
    mouse.min.js:1 Failed to load resource: the server responded with a status of 404 (Not Found)
    sortable.min.js:1 Failed to load resource: the server responded with a status of 404 (Not Found)
    menu.min.js:1 Failed to load resource: the server responded with a status of 404 (Not Found)
    autocomplete.min.js:1 Failed to load resource: the server responded with a status of 404 (Not Found)
    postbox.min.js?ver=4.9.7:1 Uncaught TypeError: a(…).sortable is not a function
    at Object.init (postbox.min.js?ver=4.9.7:1)
    at Object.add_postbox_toggles (postbox.min.js?ver=4.9.7:1)
    at HTMLDocument.<anonymous> (post.min.js?ver=4.9.7:1)
    at i (jquery.js?ver=1.12.4:2)
    at Object.fireWith [as resolveWith] (jquery.js?ver=1.12.4:2)
    at Function.ready (jquery.js?ver=1.12.4:2)
    at HTMLDocument.K (jquery.js?ver=1.12.4:2)

    • This reply was modified 6 years, 1 month ago by fwade.

    That worked for me but only partially… the editor can be used but some of the buttons aren’t working, such as Add Media. All plugins are deactivated and I am using the twentyseventeen theme.

    Any ideas?

    fwade

    (@fwade)

    On my computer, which is running Chrome, I have the same problem but I found a fix that’s a silly one.

    Hover over the Add Link button in the Insert/Edit link box and if you carefully focus the end of the arrow over the very bottom edge of the button, the arrow turns into a clickable finger. This may work for you – it certainly works for me.

    Thread Starter fwade

    (@fwade)

    I found the answer — I am being hosted by GoDaddy and here is the answer posted up by another user that worked for me.

    I’ve been using GoDaddy for over 10 years, and for over 2 with WordPress.

    Changing the permalinks from the default to any other custom version DOES work – you really just have to wait a few minutes for it to all resolve on the server.

    Trust me – set them to your “pretty” version and load up your page. Click around, get your “404” errors, and then go grab something to eat.

    When you come back, it should all be resolved.

    If for some reason it takes more than half an hour (which it’s never taken for me – usually less than 10 minutes), there may be other issues with your hosting setup, or your installation. But for me, time and time again, it’s just a matter of patience. 🙂

    Forum: Your WordPress
    In reply to: Help Needed

    Oh my goodness — thanks for this! It worked perfectly as a fix to my own problem!

    I had no idea it was a GoDaddy delay!

Viewing 9 replies - 1 through 9 (of 9 total)