Forum Replies Created

Viewing 15 replies - 1 through 15 (of 20 total)
  • Thread Starter ashiado

    (@ashiado)

    Sorry to bother you with another question: Could you just quickly describe what happens if the plugin has been activated but then later gets deactivated or uninstalled, (for example in case at some point in the future there is a conflict between your plugin and another plugin that becomes needed for some reason)?

    Does the website code (css, inline-css, etc) revert to the way it was before the initial plugin installation and activation? Or does the website code stay the way it is?

    Thanks!

    Thread Starter ashiado

    (@ashiado)

    Aha! In fact two websites where I am having issues use the Enfold theme. I will look into whether it is possible to disable the javascript uploader function. Given that Enfold makes a big deal about GDPR compliance, hopefully they will also facilitate tools for the disabling of Google Fonts (and other fonts like FontAwesome).

    In any event, I think any theme developer who is able to put out a high-quality, fully GDPR compliant theme in the near future is going to stand to make a LOT of money, because trying to retrofit existing websites so that they are compliant is a massive pain in the you know what. I personally would almost rather do a redesign.

    Thanks again for the great plugin and super helpful follow-up. I’ll recontact you as I gather further info on my current sites with respect to how the plugin is working.

    Thread Starter ashiado

    (@ashiado)

    Thanks very much for your response!

    A follow up question: I have the plugin installed on a couple of different websites and in some instances it seems to work absolutely perfectly (according to Pingdom), but in others it does not, even for a site that uses an up-to-date good quality theme. I would give you a link but I’d prefer not to post the URL publicly. Possible to email you? Or are there any ‘obvious’ troubleshooting tips you might recommend?

    Thanks again!

    777 definitely is not a good idea, but with some web hosts, that’s all that will work. I would contact your web host to ask for support. If they can’t fix the issue, then… if I were you I would switch web hosts, but obviously that’s something you would have to evaluate and decide on yourself.

    You’re welcome. I hope of course that it works for you as well!

    One addition: This is probably obvious but just in case.. If you have your wordpress installation in a directory that is *not* your site root, then you will need to include that in the upload_path. For example: “/home/[WEBHOST-LOGIN-NAME]/public_html/[WP-DIRECTORY]/wp-content/uploads”

    Thread Starter ashiado

    (@ashiado)

    Hello again,
    On my end — at least for my case(s) — I think I have it figured: On multiple different installations of wordpress (for different domains and with different web hosts), the content of the database field upload_path (within the wp_options table) got changed/corrupted in the process of updating to WP 3.8. Please note that the upgrade process corrupted this field *differently* depending upon the site and upon the associated web host. In some cases the content of the field was deleted entirely. In other cases, *portions* of the path from the end or from the middle were deleted or added onto. ALL of these websites were working *perfectly* in terms of image uploads before the WP 3.8 upgrade. The fix I used: By directly editing and updating the upload_path in the database, I was able to resolve the problem. As mentioned above, what this path should read will depend upon your web server, as it depends upon its configuration. If you don’t know what this path is for sure, then probably easiest to contact your web host and ask. However, the ending of that path should be “wp-content/uploads”. For one site, for one particular web host, it was “/home/[WEBHOST-LOGIN-NAME]/public_html/wp-content/uploads”. After I made this fix to the database, I also rebuilt my permalinks just for good measure, then also logged out of WP, cleared my cache and logged back in. I hope that this helps some ones of you out there. Good luck.

    @souldancer, I have been having a very similar issue on a number of sites and just now, at least on one of them, I was able to fix one part of the issue. On my end it looks like the WP upgrade process corrupted the data that was contained in the upload_path field within the wp_otions table of the database. When I fixed this path, the issue (partially) resolved on one site I have tested. Note that I am still testing(!) but thought I would share this for you to possible check on and/or try. The path that should be indicated in this field is (I believe) the server path, not a straight URL, and it should end in “wp-content/uploads”. I am still having some other image-related issues with WP 3.8, so I do not want to call this “resolved” at this point, but maybe it is a small bit of headway.

    I am having the same issue as soledancer and it is affecting all of the WP sites that I updated to 3.8 yesterday.

    FYI, I have already tried deactivating ALL plugins and switching to the default theme. I also cleared caches, etc. These steps did *not* fix the problem.

    Assistance with this would be greatly appreciated!

    Finally SOLVED by installing the Core Control plugin and then following the directions here: https://www.ads-software.com/support/topic/231500?replies=12#post-1168609

    Beautiful! Thank you!! Solved my plugin and WP version update problems and all is working much more quickly too!

    THANK YOU!!!!!!!! This solved the problems I was having re: using WP’s autoupgrade function as well as re: auto-upgrading plugins. Appreciate it very much!! ??

    i tried the edit to the class-wp-upgrader.php suggested here: https://ocaoimh.ie/wordpress-mu-2-8-3/ but it still didn’t work.

    I also carried out a manual upgrade to 2.8.3 on one of the three WP installations relating to this domain, and that didn’t fix it either.

    Six hours later…big sigh. Time for a break. Help?

    I just came across this month-old thread on the topic, but the http.php fix proposed in it is not working in my case. Just FYI for anybody else who comes across this!
    https://www.ads-software.com/support/topic/278487?replies=38

    Follow-up to my above message: I just triple checked that all my plugins were up-to-date and they are. I also tried deactivating all my plugins, logging out, then logging back in again: same issue. Then I tried changing the language preference in the config.php file from French to English — no difference. I’ve double checked file permissions too.

    Anybody else out there having this problem or have a suggestion for a fix? It seems like a significant security issue, because if I didn’t happen to have other WP installations going that DON’T have this problem, i probably wouldn’t notice that WP had been updated, or any of my extensions for that matter, because no notification shows up…

    Thanks!

Viewing 15 replies - 1 through 15 (of 20 total)