Viewing 7 replies - 1 through 7 (of 7 total)
  • erfii

    (@erfii)

    I experience the exactly same issue.

    But it’s a bit tricky beside that. I have multilingual setup with wpml. Every language has it’s own domain.

    .de is root-domain, .com points to the root. So there is only one wordpress installation.

    With .de everything works fine. But if I change to .com the error with the double url prefix happen. I get cdn.cdn.url.tld instead of cdn.url.tld

    Plugin Author Raul P.

    (@alignak)

    Will look into this for the next update, in a couple of days.

    Plugin Author Raul P.

    (@alignak)

    should be working on v2.2.3, thanks

    Thread Starter golusinghcpr

    (@golusinghcpr)

    An another issue : on clearing cache it always shows “Purge FVM cache directory (6.43 MB)” , even if you click on delete button again and again.

    Plugin Author Raul P.

    (@alignak)

    @golusinghcpr that means, PHP doesn’t have permissions to delete the files.

    Make sure you recursively chmod 777 or 755 wp-content/uploads/ and that the message goes away when you purge the cache.

    Thread Starter golusinghcpr

    (@golusinghcpr)

    wp-content/uploads and FVM both directory have the same permission 755 already set.

    Plugin Author Raul P.

    (@alignak)

    then try 777, because the plugin cannot delete the files.

    Do you see the files on the directory, when you login via ftp or through the file manager at your control panel?

    If the files are gone and the plugin still says it’s not, then it’s related to your server object cache. Some servers and providers, cache information about certain operations, such as directory or file sizes.

    On some providers you can even delete the whole wordpress site and it still shows as usual, because the php code is already cached on the server.

    I’ve seen very frequently, people deleting plugins and purging their cache multiple times, but wordpress still thinks the deleted plugin is there.

    Take a look at the server info tab and see if the paths are correct.
    You can also try to set another cache location on the plugin settings.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘New Update Messed up all the things’ is closed to new replies.