Rick Curran

Hi, thanks, yep, that’s definitely one option. I would prefer a method that doesn’t involve translation strings ideally do to the rick that this could be overridden by a language update in Contact Form 7.

I was hoping there may be an action / filter that can be used to modify this instead.

Thanks @timwhitlock, I’ve modified that code for now and that has let me go back to the previous ordering method based on the order they appear in the templates.

It would be useful to have some form of filter or control for that sorting to save having to change it in future plugin updates, I don’t usually generate PO files that often but with the current development schedule of a project I’m working on it is likely to be a recurring process.

Thanks again for your prompt help!

• This reply was modified 4 years ago by Rick Curran. Reason: Minor Clarification

Hi Takayuki, thanks for replying!

I was going to send you a link to view the form but as I had installed the “ReCaptcha v2 for Contact Form 7” plugin to get the form working I went and removed it and then set up new Recaptcha keys in the Google admin. After putting in these new V3 Recaptcha keys the form seems to be submitting ok now!

So I guess for now I’ll keep an eye on it, I know before when it was failing to send it was failing for other people in other locations and not just me on my computer, so it definitely didn’t seem like it was just seeing me as a spammer somehow. Is there anyway I can debug it if it does start seeing submissions as spam again?

Thanks for your help!

Hi,
Just marking this issue as resolved now. The fix here was to de-activate and delete the plugin and then flush all of the LiteSpeed options from the wp_options table in the database, then reinstalling the plugin. Doing that seemed to do the trick.

Hi,
Thanks for the reply. I’m afraid neither of those made a difference. It cleared the cache but it’s back again as soon as I view a page. Basically none of the plugin settings seem to do anything, if I deactivate the plugin it stops caching but just activating the plugin but with cache settings to off it still just caches everything.

Rick

Hi,
Herein lies the problem, the cache *is* disabled, all of the plugin settings are set to ‘off’. Yet, the pages served up are definitely being cached and delivered from the cache:

x-litespeed-cache: hit

Here are screenshots of my plugin settings:

Cache Off
Cache Purge off

Hi Philipp, thanks for getting back to me. I understand the issue with compatibility with Gutenberg, I am indeed still using the classic editor on the posts that this is on.

From a security perspective I consider a security plugin to be doing its job if it is warning me of plugins that are potentially going stale so in this it’s a fair warning. At the moment the repository indicates that it has been 2 years since your plugin has been updated, I appreciate that your plugin can’t be simply updated to support WordPress 5.* but an update to the latest version prior to V5 (4.9.12) along with a note in the description to indicate that it doesn’t work with Gutenberg would at least get the last-updated date to be more recent. The Classic Editor will be supported until Dec 31 2021 so in theory people could still be running your plugin for some time.

Thanks again for the response!

Hi @supernovia, yep, it seems a bit of a strange one to me too! I don’t have time to try and dig into it any further but at least it’s working ??

Hi @supernovia, I’ve installed the Health Check plugin and tested it out and the “Older posts” function worked fine using the default theme, I went through the plugins and enabled them one by one and checked as I went along.

In the end I had them all enabled and then switched back to the main theme and after that it appears to be working correctly on the main theme again!

I haven’t changed any code at all in the theme so I wonder if just the process of disabling and re-enabling one or more plugins has cleared something out in the process – either way it’s working again now so I’m happy with that for now.

Thanks for your help!

Hi @supernovia, no, there has been no change to the theme at all for quite some time.

Actually the main issue I’m trying to resolve here is the ‘older posts’ button not loading posts, the issue with the connection to WordPress.com not showing on the Jetpack debug page is a secondary issue – I’m not sure why it’s not showing as connected in the debug page but it definitely is in the back end of my site.

To restate what I said in my initial post I can see that the infinite scroll function is actually getting the older posts as I can see this when I inspect the page with web inspector and look at the AJAX / XHR requests. There is a successful request to get the next 10 posts but for some reason it is not getting appended to the page content, there’s no errors in the console at all, it just silently fails.

Hi James,
Thanks for the reply, I noticed too that it doesn’t show up as connected when using the Jetpack debug page, however it definitely is connected and just to be sure I went and disconnected and reconnected again. It is still showing as not connected in the Debug page though.

Screenshot of connection to wordpress.com

Ah yep, I can confirm that these field title strings are in the database so they don’t get translated.

My only choice in this instance was just add the translations for the four field titles using language-specific CSS, I added ‘after’ pseudo-elements onto the form labels that the titles appear in (Username, E-mail, Password, Repeat Password) and using content: 'Thai text here' to put the text in place, making the original text colour transparent so it doesn’t show.

A bit of a hack but the only way to do it for now.

Not urgent on my part any more but a feature request would be to see if these strings can be pulled out of the database and passed in as string instead, I’m not 100% sure why these have to be in the database at the moment but it does mean that this plugin can’t be 100% language switched on the fly.

Ah, ok. That’s unfortunate. I’m not sure what to do now as I really need to be able to translate these names as well. Would there be any way I could programmatically override these in my own code?

Hi Gabriel, thanks, I’d seen that those fields are all in the “Form Fields” section so I thought there must be some relevance to the issue here.

However, I’m confused as these strings do appear to get translated in your plugins code don’t they? Are you saying that whatever language these form fields are set / using will not get changed even for people using the standard translations you supply with Profile Builder?

Hi, thanks for the suggestion. I’d previously done those steps but I’ve gone back through them again just to triple check ??

I’m definitely running the latest Profile Builder 3.0.1 and I’ve done steps 2, 3 and 4 but I’m still only getting a couple of translated strings through.