I'm using Contact Form 7 + Friendly Captcha along with SMTP-Mailer. It's working fine for me.

https://wordpress.org/plugins/contact-form-7/
https://wordpress.org/plugins/friendly-captcha/
https://friendlycaptcha.com/

@girish sorry for the long delay in answer, many many thanks

@scooke Ah! Ok, I will try this, thank you!

@zappy for WP migration, https://docs.cloudron.io/guides/migrate-wordpress/ is maybe a good start.

Cloudron annoys the hell out of me if I/Cloudron doesn't control the DNS. Please allow me to make it stop.

Not sure what annoyed you 🙂 Happy to fix whatever that is, but otherwise, you can always change the DNS provider to 'manual' and then Cloudron won't touch your DNS.

Nextcloud limitations. There doesn't seem to be a nextcloud-dev version that lets me have plugins and do custom stuff without a ton of steps.

By nextcloud dev, do you mean just having a "playground" nextcloud installation ? We do this usually using "clone" functionality - https://docs.cloudron.io/backups/#clone-app . That will create an exact replica of your existing app into another location and then you can tinker on a non-prod instance.

@zezaung hey sorry been sick today so I've been sleeping what page had the issue? Cause the site loads great for me

@girish Yep, that worked! Thanks a lot.

@d19dotca whoops, looks like some network retry from my browser. did not notice! i removed the dup.

FYI - related discussion: https://forum.cloudron.io/topic/5960/setting-memory_limit-dynamically-in-wordpress-developer-package

@humptydumpty adding another layer will have some performance impact but it should be barely noticeable (plus the security benefits of such a setup are immense). nginx does nothing other than https <-> http on Cloudron.

@martinkbs & @girish - So I found the documentation for WooCommerce which does seem to state that it uses the time zone: https://docs.woocommerce.com/document/smart-coupons/how-to-set-expiry-time-with-the-expiry-date/

However that definitely wasn't my experience. Here's a screenshot I took yesterday and meant to include in my original posting, showing the local time zone not yet at October 1st but the server time was October 1st, which is why I strongly believed the code was marked expired because it was looking at the server time instead (it was the only explanation that made sense):

Screen Shot 2021-09-30 at 9.35.52 PM.png

I have created a new coupon code for them which I set to expire on November 1 so I'll try to remember to test out later in the evening of October 31st. I'll also try to duplicate this website to a staging domain and test as well as that'll probably be much quicker so I won't have to wait 😉 hahaha. I'll try to report back with my test results.

@d19dotca Yes, this means that the app can be configured so that the admin can take total control of the mail configuration inside WordPress. See the "Optional Email Configuration" section in the latest release - https://blog.cloudron.io/cloudron-6-3-released/

If you configure WP as "Do not configure mail settings", then you can install another WP mail plugin and manage it entirely yourself. For example, you can also send emails directly via sendgrid/SES etc instead of via Cloudron mail server as well.

@girish Thank you its all working now.

@nebulon I have identified that it is an issue with multisite and the setting

define( 'DOMAIN_CURRENT_SITE', 'xxx.de' );

in the wp-config file. This does not seem to be getting updated automatically and hence the change needs to be made manually (and also in the database).

Sorry, I didn't mention that it was a mutlisite installation before because I couldn't see any reason for that to affect the smtp plugin settings.

@girish ok, done. Email sent to support@

@jdaviescoates Yes you are right thanks. I guess I got confused because I feel it's strange that users from Cloudron are not fully carried over to WordPress instances if you understand what I mean, although I still may need a bit more of a refresher.

Actually, with all the devlopment work going on, it is a wonder anyone can keep all their crucial security information up to date.

Thanks for the help - this topic is closed as far as I am concerned.

The file /app/data/public/.htaccess will automatically be updated with the below when the permalink structure is changed. If you imported from another install, can you please check if your htaccess has this? You can check this file using the file manager

# BEGIN WordPress # The directives (lines) between "BEGIN WordPress" and "END WordPress" are # dynamically generated, and should only be modified via WordPress filters. # Any changes to the directives between these markers will be overwritten. <IfModule mod_rewrite.c> RewriteEngine On RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}] RewriteBase / RewriteRule ^index\.php$ - [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php [L] </IfModule> # END WordPress

334cb414-c5d1-4ee4-9bf9-9c886dd2e293-image.png

I have fixed this for the next release.

@lonkle I forgot I turned automatic updates off, Domain Aliases are supported in v6.1.2. 🤦

But on top of that, you should note that you only enabled Domain Aliases on subdomain multisite installs, not subdirectory multisite installs. Both of those types of Multisite Modes support multi-domains. That's important to note since many like to use subdirectories and still use multiple domains.

@jdaviescoates Possibly.. I expanded the guide to outline both the approaches now.