iWPer

As you replied so promptly before: does this topic still come up in your list of active threads?

Hi Beatrice,

Thank you for your prompt reply.

The option No Access Modal is not checked.

Hi Frank,

Your fix worked for me! Thank you for your quick help!!
Can I use this fix now and expect the next update to include it?

Have a good weekend!

Thanks.

This did not happen in 2.0.2. I noticed and checked after the update messed up the layout, because the font was not loaded.

Regards

Thank you!

I know how to check the attributes when the shortcode activates my function. I was just hoping that I was missing something about has_shortcode (or a similar function) that could help me to check for these attributes earlier in the loop.

I have now added an extra option in the plugin-settings-page.

Is it just a restriction, because the email address cannot be checked, or is it not yet possible to call other vallues as the “to” email address upon submit?
Could you point me in the right direction to code a temporary solution?

Thanks

I will look into this further.

Is the collected user-data, inside the HTML of the webpage, the only dynamic part which would (normally) require a page to be generated, rather than static?

Thanks

P.S.: Any news on the translations or possibility to change messages for the front-end? See “Dutch translation”

Thank you!

I had to enable this function first, to see the lines you mentioned.

On the homepage it does not show anything like this.
All other pages do show these lines, except for one, the contact-page.

The homepage and the contact-page have one thing in common; both have a form which generate/fetch some user-data inside the HTML. This might very well be causing my issue.
The user-data is not being used, so if the plugin would allow me, I could disable it.
The plugin is PlanSo Forms Pro. I don’t see any option to disable the user-data fetching.
Changing the plugins files is not a very feasible option, the plugin is updated quite regularly. Unregistering a function may help, but I don’t know what instructs WP Super Cache not to cache these pages, or does WP Super Cache detect the user-data requests and decides not to cache these pages? The lines don’t seem to be added using a separate function.

Thanks

Anyone know the “filename” to add to –“Add here those filenames that can be cached, even if they match one of the rejected substring specified above.”– to force the homepage to be supercached?

Any alternative method to accomplish the same is very welcome.

Thanks

Hi Laura,

Maybe your theme has a custom admin-bar. This could override default buttons or buttons from (some) plugins.

Hi,

Thanks for your reply.

I have seen the option to exclude files, but somehow missed the option to include them.
I just tried it but did not get it to supernate the homepage.

I knew about the clear all cache pages but was unsure if this would also clear the supercache. I had an issue with this before and am not sure if I then had it enabled or not.

I have a daily preload interval. This should be long enough and prevent possible issues from lasting longer than a day; unless it is caused by something else of course.

I knew this option; just figured it might be helpful to mention.

Thanks again for your clear instructions. Any clue on how to get the homepage to supercache?
I did find the rule which causes this “issue” (for my situation) but changing it in the plugin files is not very helpful because it will be overwritten on every update of the plugin.

Thank you for your quick response.

Whatever is the quickest, would be best for us. But if the customizable front-end messages are coming shortly, it would be double work to make these reduced translation files for one (or a few) users.

If the list with front-end messages is not to long, I wouldn’t mind doing all of them so other user may benefit from this as well; we only need 3 messages translated to dutch.

Let me know if the “planned” feature is coming shortly or if it would be best to make these few translations first. If the former will take longer, you could send me a list with front-end messages to translate.

For us, we only need the next messages translated:

EN – Attention! There has been an error submitting the form. Please check the marked fields below.
NL – Niet alle velden zijn correct ingevuld.

EN – This field is required
NL – Dit veld is verplicht

EN – Invalid E-Mail
NL – Ongeldig e-mailadres

Thanks!

Same here…

Done; sorry !

Seems like an easy fix; this line,

if($signature->optin = 1){

has to be replaced by,

if($signature->optin==='1'){

Good luck