Forum Replies Created

Viewing 15 replies - 1 through 15 (of 17 total)
  • Thread Starter sunb1

    (@sunb1)

    Sorry about the delay, holiday stuff got in the way.

    I got curious after my comment about possible differences in configuration or environment so I tested your plugin on another site of mine (different server), and the issue did not occur there.

    Went back to the original site, I did some cleanup, so I can’t say with 100% certainty which step resolved it, but one key change was deleting all plugin-related entries from the database and then uninstalling and reinstalling the plugin. After doing that, the custom source now stays in the field correctly after saving.

    It’s possible your last update already fixed the underlying issue and it just needed a clean install rather than an update over existing data, Not totally sure about that, but things look good so far.

    I’ll test more when I have time, but for now everything seems stable.

    Thanks again for all your help, and happy holidays / happy new year.

    Thread Starter sunb1

    (@sunb1)

    Well, after a few hours of testing (it’s become a challenge lol), I’m still seeing the same issue. When I add a custom source (e.g example-csp-test.website.com) to a directive and save, the value is stored in the database (confirmed this) and correctly appears in the CSP header, but it still disappears from the URL field on reload after saving. No caching is being used now (admin not cached; LiteSpeed/Cloudflare bypassed), and this is the same across different browsers. The duplicates are probably harmless since they’ll be ignored, but the disappearing value is a major problem as if I press save again for any reason, the custom entry gets removed because it’s no longer in the field.

    I think since the entry shows up correctly in the database and on the front end, the plugin is working as it should, but there may be an issue in the UI. Could also be due to differences in configuration or our environments, which might explain why it works for you but not for me.

    Thread Starter sunb1

    (@sunb1)

    I always clear all caches (browser, litespeed etc) between each change but i’ll dig deeper. Will let you know what i find. Thanks

    Thread Starter sunb1

    (@sunb1)

    So updated php and no longer getting incompatible message. Updated, cleared cache and tried the ‘font source’ field and for me it’s still doing the same thing:

    Original entry: data: https: *.gstatic.com fonts.gstatic.com cdn.jsdelivr.net *.bootstrapcdn.com

    Tested by adding a font source url and after hitting save it dissapeared from the field but source did show it updated but also shows https: and *.gstatic.com duplicated. But the url field does not show them duplicated so not sure how to get rid of them:

    font-src ‘self’ data: https: *.gstatic.com fonts.gstatic.com cdn.jsdelivr.net *.bootstrapcdn.com https: *.gstatic.com ;

    Deleting the whole field also results in them coming back after save lol. Will test more tomorrow but can you confirm it’s no longer doing this in your testing?

    Thread Starter sunb1

    (@sunb1)

    @kevp75 Thank you for the quick response and fast fix — much appreciated. It looks like I need to update my PHP version, as the latest update isn’t compatible with 8.1. I’ll update both and let you know if I run into any issues.

    I’ve updated my review as well — the plugin and your support definitely deserve 5 stars. (actually for whatever reason it won’t save my edit. I’ll keep trying)

    Thread Starter sunb1

    (@sunb1)

    Just to add, its happening in other url fields also.

    Thread Starter sunb1

    (@sunb1)

    Hi,

    Thanks for the reply and the suggestions. Looks like as a workaround that will work.

    But, yes I think it would be great to have a manual share button.

    Thanks

    Was about to post about the same thing. Just cleared 8GB from the error file because of this.

    Thread Starter sunb1

    (@sunb1)

    So basically what you are saying is that you fixed the issue of the field not being clickable/editable but also took away the option away from the free version and now the only way to use it is to buy the paid pro version?? The fallback image you linked is global and not per individual feed. Taking this option away as per your explanation really makes no sense.

    This makes your plugin no longer useful on any of our sites then.

    Thread Starter sunb1

    (@sunb1)

    Hi, the field is clickable now but did you remove the ability to use a image url now? The field help text now only states: You can use the magic tags, or leave it empty.

    It does not mention being able to use a url anymore? A test post also resulted in the image not being set.

    @maya Interesting. Will install again and test it out that way. Thanks

    Hi, was about to post about the same issue and even after enabling that new option (WP Hide > Login / Admin > Admin URL > Disable Admin Url redirect to Login page), I found at least 3 places with the new admin url was exposed. Once by our theme and 2 by different plugins.

    I’ve disabled the plugin for now since it’s not working but it would be great to find out how to fix this issue. Thanks

    @semoliner Checked for you and yours is still exposed also.

    • This reply was modified 2 years, 1 month ago by sunb1.
    • This reply was modified 2 years, 1 month ago by sunb1.

    Just made a post about the same thing. 100s of duplicates. Did anyone get this resolved?

    Thread Starter sunb1

    (@sunb1)

    So i’ve done a through check of the app that doesn’t work and compared it to the other one that does. The only difference is that the one that works is still using Graph API v13.0 while the one that doesn’t work is using v18.0. Just thought i’d mention it in case it had something to do with it.

    • This reply was modified 2 years, 1 month ago by sunb1.
    Thread Starter sunb1

    (@sunb1)

    Hi, Thanks for the reply. I’ve gone through all those steps and more a few times and still the same issue.

    If I de-authorize then a message does show up in the ‘select Facebook pages for auto publish’ box stating:

    Failed to fetch pages. validating access token: The user has not authorized application

    But once authorized, no pages are there. I’ve exhausted all the troubleshooting so i guess the plugin just won’t work on this site for some reason. I’ll have to switch to another plugin in the meantime but will circle back if the issue ever gets resolved.

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