Forum Replies Created
In reply to: [Contact Form 7] Previous Required Fields Validating Automatically
I see that you asked for an example that demonstrates this problem, but didn’t receive it yet. Well, here is an example:
If you want I will be happy to send you the source code of the WPCF7 form template used on this post; please let me know where to send it.
In reply to: [WP-Optimize - Cache, Clean, Compress.] loco-translate
I guess you intended to write: “The plugin name is not in gettext function call, so I suspect you canNOT translate the name.”
- This reply was modified 4 months, 2 weeks ago by Henk Barreveld.
Thank you for your immediate reply and quick action!
I am looking forward to the new release. For the time being I have re-installed version 3.2.3.
Were you referring to release 3.2.6 with release date June 15th 2022 on wordpress.org?
If so, then I am sorry to say that it looks like the fix has not worked, or at least not completely. I get four messages
Backend log: [ERROR] : WP_CACHE constant is not present in wp-config.php
every time I activate WP-Optimize.
- This reply was modified 5 months, 2 weeks ago by Henk Barreveld.
Thank you for your reply. Please let me explain a little more…
I mentioned (well, intended to make you aware of :-)) three issues:
- Both the
configname and the
configcontents include the website domain. This makes the
configunusable after migrating the site to another location. However, looking at the
configsettings, I have the strong impression that it could very well be used on the migrated website as well.
- You write that the
configis generated on the fly, but in my experience it is only generated when you save the Cache-settings. The fact that there is no (suitable)
configis unclear to the user (website manager). It is only because I configured my server to send me an e-mail on cron-output that I noticed this error message – and the error message does not make clear that I should re-save the Cache-settings.
- The fact that settings in
configcan be different after installing an upgrade means that after an upgrade you have to rebuild the
configby re-saving the Cache-settings. That is not clear.
It seems to me that all of this could be handled by simply having WPO create a new
configautomatically (!) if it is missing or after a plugin update.
Thanks again. Problem solved – my bad…
- I set up a new, empty site, theme Twenty Twenty-Two, only YDP plugin ad found that cloning clones produces slugs as desired, e.g. test, test-2, test-3, etc.
- I set up a copy of my problem site, disabled all plugins except YDP and selected theme Twenty Twenty-Two: wrong result (slugs test, test-2, test-2-2, …).
- Then I compared the YDP settings on both installations, and found that on the problem site the setting “Duplicate Post > What to copy > Slug” was checked. After unchecking this, the desired slugs test, test-2, test-3,… are produced.
So the solution is to make sure that copying of the page/post slug is not set. Obvious, when you think about it.
Thank you for your help!
- This reply was modified 8 months, 1 week ago by Henk Barreveld.
Sorry, but I think you are mistaken.
This is what WordPress does when YDP clones a post:
- original post:
- clone of original post:
- another clone of original post:
That’s also what you write – but that is not what I wrote about.
People want to clone the most recent clone instead of the original post, for example because it is the easiest one to find, because it contains the latest version of the desired layout and fixed content parts, etc. If you ‘daisy-chain’ the clones, so to say, WordPress produces URLs ending with -2, -2-2, -2-2-2, etc.
Please have another look.
- This reply was modified 8 months, 2 weeks ago by Henk Barreveld.
If someone would like to be unsubscribed from all lists, they can change their status to “Unsubscribed” or click on the “Unsubscribe” link from your newsletter.
Sure! – but that’s not what I meant. People may want to unsubscribe from all lists they get presented in the Manage Subscription form, but they may need to keep their subscription to other lists which are not on the Manage Subscription form.
Thank you for looking into this. I’m looking forward to the solution!Forum: Plugins
In reply to: [Akismet Spam Protection] View email blocking results
Well… I did not get the number 39,000 from Akismet; it was the number of spam-comments WordPress reported on the Admin area > Comments page.
In the meantime I looked into the Contact Form 7 code and it is clear to me now how this works. I might be able to use some CF7 hook to collect the information myself or, indeed, I could use the Flamingo plugin.
Thank you for your help!
Thank you! Message to premium support has been sent.
In reply to: [Akismet Spam Protection] Contact form author domain problem
Just tested: working!
Thank you very much for this super-fast service. I will mark this as “resolved”.
You are right. after upgrading WP-Optimize from 3.1.8 to 3.1.9 I still get the same robots.txt file:
User-agent: * Disallow: /wp-admin/ Allow: /wp-admin/admin-ajax.php Sitemap: https://xxxxxxxxxxx.nl/wp-sitemap.xml Disallow: /uploads/wpo-plugins-tables-list.json
Maybe I should explain better what the problem is with this. Unless I am completely mistaken, the path in the
Disallowdirective should be relative to the website root folder. However, unless the default path of
uploadshas been changed in the WordPress theme or so, the folder
uploadsis not in the website root folder, right? It is in
wp-content. So the directive should be (default):
By the way, a quick look at the plugin source code shows another problem: for this additional line in robots.txt, WP-Optimize does not take into account that on a WP site the location of the uploads folder may be non-default. It does recognize that possibility where it uses the file
Thank you @stevef2,
However, I am afraid that in the meantime I found that this is not a complete solution.
If you want to clone a site on Local (or export it, to be imported later again, maybe under a different name), you must first first remove the port number from the DB_HOST definition in wp-config.php! Afterwards you can of course set the port numbers again – making sure that you use the right number for each site.
What is behind this…
I checked the MailPoet source code. For the way it accesses the database, I understand it needs to specify the port number. They do that with the data provided by wp-config.php: if DB_HOST includes a port number, then that is what it uses and otherwise the default 3306.
In principle this is all right. According to the docs, WordPress expects that the port number is added to the DB_HOST constant if the database is not accessed using the default port.
The Local software does not use 3306 but different port numbers. They have to, in their implementation, because they use a different port for each site you create on Local. However, they do not require you to specify this different port number in your wp-config.php file! Somehow, ‘under the table’, they correct for this. I suppose this is for better compatibility with live hosts on Flywheel and WP Engine (where the port numbers will be different – probably everywhere the default 3306).
And so there is a problem. If, on Local, you do not include the port number in DB_HOST, MailPoet does not work. When the port number is specified, cloning a site or export/import of a site does not work, probably because the copy has the same port number in the wp-config.php file as the original.
I think this should actually be solved in Local rather than MailPoet…