shamank

Any update on this?…

Any updates on this? I followed @wasilij instructions to temporaly disable this malfunction on blog posts:

Thank you, it worked

Just in case, updating the plugin fixed the issue of the form. Thank you!

Well, it started to work. Cache maybe? I had an old version, which failed to upgrade, so I manually removed it and then installed the new version. Something weird in the middle… But it is unrelated to the other issue, so I’ll check it in a while. Thanks!

Hi! Thank you for your fast answer. There’s a new issue now. The plugin stopped working with the error message “Domain name does not match the actual domain”. It is because:

admin/class-aws-cdn-admin.php:
1019         $domain = sanitize_text_field($REQUEST['domain']);

And it’s empty, since the request you are sending is:

action: wpaac_list_cdn
wpaval[domain]: ***
wpaval[accessid]: ***
wpaval[secretkey]: ***

So this fails:

1060         if($check == "checkaws")
1061         {
1062         if($domain != $this->wpawscdndomain)
1063         {
1064         echo "<div class='alert alert-danger'>Domain name does not match the actual domain</div>";
1065         wp_die();
1066         }

• This reply was modified 3 years, 1 month ago by shamank.

Hi! I’m facing the same issue. I’m not being able to fix this issue with this. I’ve added “wp-login” since it’s the target of the form element but it’s still replacing the URL.

Any chance the author of the plugin may fix this issue please? I think there’s no any valid case for a form link to be replaced with a CDN domain.

Thank you!

The problem is here:

admin/meta-box-class/my-meta-box-class.php:
1010     || ( ! check_admin_referer( basename( __FILE__ ), 'at_meta_box_nonce') )    // Check nonce - Security                                                                  

Deleting that line solves the issue.

I don’t know why CTP_AT_Meta_Box->save() is being triggered when saving the form but I won’t investigate further than this. Please consider solving it. If you need something else feel free to contact me.

Thank you.

• This reply was modified 3 years, 6 months ago by shamank.

I have the same issue. When disabling the plugin I can save again. It’s definetely something with the plugin. The url is: https://new.mugendo.es/wp-admin/admin.php?page=wpcf7&post=11445

Here is a demo: https://nimb.ws/1e6r2U

• This reply was modified 3 years, 6 months ago by shamank.

You can fix it like this:

.ebg-br-wrapper > .ebg-br-background-image {
  height: 33px;
  left: auto;
  right: 0;
  width: 33px;
}

Thanks. I think you’d need to add this in some docs. I checked plugin code yestarday until I finally found the answer myself (I was about to make a post today about it), but most of people using wp are not devs and can’t do that. I couldn’t find any docs about your plugin, more than support page itself. Did I miss something? Thank you.

@alberto3 Exactly!

Mmm maybe there’s a misunderstanding here… I’m not sure my point is being understood, or maybe I’m not understanding you?. My english may not be the best (I’m a spanish native speaker).

I’m not referring to categories or tags, that works good as always did. What I’m saying is related to cache of views in mapped domains. I’ll try with this example:

Case 1: Drop cache for single page.

1. I Have my main domain “mydomain.com”, which I use to host several landing pages. One of them is called “Page A” with URL “/aaa”. So when I go to “mydomain.com/aaa” I see that page (Page A).

2. I have this multidomain plugin, which I use to map/connect “mydomain.com/aaa” with “aaa.com”. So when I go to “aaa.com” I see the contents of “mydomain.com/aaa”.

3. Fastest cache: When I go to “mydomain.com/aaa” it creates a cached view in “wp-content/cache/mydomain.com/all/aaa/index.html”, so it serves this view, which is ok.

4. Fastest cache: When I go to “aaa.com” it creates a cached view in “wp-content/cache/aaa.com/all/index.html”, so it serves this view, which is ok.

5. I make a small change in “Page A”, so I want to drop the view cache for only this page (like saving, with the proper config in Fastest cache plugin, or just hiting the button to drop only cache for this single page, like the link you provided with tutorial).

6. Fastest cache: it deletes the view in “wp-content/cache/mydomain.com/all/aaa/index.html”, so if I go to “mydomain.com/aaa” I see the applied change. This is ok. However, it doesn’t delete “wp-content/cache/aaa.com/all/index.html”, so if I go to “aaa.com” I’ll still seeing the old cached page, with the old contents.

—

Case 2: Drop all cache

1,2,3,4 => same as before

5. I make a change in a theme feature or a component that require all views to be cleared. So I hit in the top bar button “empty all cache” (I have it in spanish so I don’t know the english name… I guess it is something like that).

6. Fastest cache: it deletes all views in “wp-content/cache/mydomain.com/all/*/index.html” (all URLS, like “/aaa”, “/bbb”, “/xxx”…), so if I go to “mydomain.com/aaa” or “mydomain.com/bbb” I see the applied change. This is ok. However, it doesn’t delete “wp-content/cache/aaa.com/all/index.html”, so if I go to “aaa.com” I’ll still seeing the old cached page, with the old contents. Same if I have other mapped domains, like “bbb.com”. It only deletes all views in my current main domain “mydomain.com”.

So my proposed solution is to delete all index.html (and wpfc-minified files) in all directories, not only in “mydomain.com”, when you hit “empty all cache”.

The next step would be to clear cache for single pages (like deleting “/aaa” and “aaa.com” cached views when saving “Page A”).

Thank you.

Yes, I already do that, but it doesn’t remove cache for the associated domain, just the URL. For example, I have a landing page A in “/aaa”, and it’s connected (through this multisite plugin) to “aaa.com”. When I flush cache (single page method or full cache), it correctly removes cache for “/aaa”, however cache at “aaa.com” is still there. So, let’s say I make a change in page A, flush cache (any method), and change is visible in “/aaa” (as supposed to), but “aaa.com” is still showing the old page (forever).

I know it can be difficult to implement individual page cache cleaning to mapped domains because it’s an individual implementation for each multisite plugin. You can’t know the mapped domain unless you know how plugin made it, and they are all custom implementations.
An option could be to save the real URL path as a comment in your plugin comment at the end of the page (like “<!– WP Fastest Cache file… wp-fastest-cache-path:/aaa …” so you can grep that specific value) and then remove cache from all pages containing that URL, so you would be also removing cache layer from other mapped domains targeting the same page.

Anyways, if “flush all cache” (global) would remove cache from all pages (removing all cached views like wp-content/cache/*/all/index.html) then it would be a partial solution I guess.

Thank you!

You are absolutely right with that, but we are using Avada as the main theme and it has “global blocks” to share code among different pages (you change code in a single place instead of going one on one). We use a common block (layout) for footer and some internal elements. In those cases, I’d need to flush everything to update all views. Other case is a form reused in different pages. You change something in a form (contact form 7 page) and it must be updated in all pages using it.

BTW, it would be great to flush only the cache of a single page instead of removing the entire cache (on small modifications), but I think it wouldn’t be possible for you unless you make some special support for every multisite plugin (like the one I’m using: “Multiple Domain Mapping on Single Site” => https://www.ads-software.com/plugins/multiple-domain-mapping-on-single-site/), right? Because you wouldn’t know the mapped domain unless you query the specific plugin object.

Thank you!