@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): [image: 1633147441754-screen-shot-2021-09-30-at-9.35.52-pm-resized.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 [image: 1627595584635-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.

@girish I requested the developers to review the query. Meanwhile I changed the setting in mysql and indeed the plugin doe work now as expected!

I have tried to fix this in the latest package - https://docs.cloudron.io/apps/wordpress-developer/#email-setup-multisite . I pushed the update last week but it's been rolling out slowly. A new install (which is required for multi-site) will get the latest package.

I think the WP distribution does not have .htaccess files at all and it's only generated when you setup permalinks. I thought maybe atleast wp-content might have .htaccess inside it but even that doesn't. I guess it's up to the user to set those up, if they want to. I guess the main danger is if your site somehow allows someone to upload php files, then it might get executed under wp-content. But this of course requires one to install such a plugin that let's someone upload random files.

@robi Oh..... well that went way over my head.

@arungurume I think what nebulon meant is he put you on a premium plan with no charge until the issue is sorted out (and not the existing free plan).

@girish yeah, you have to put sftp:// when using the quickconnect because the default for that is just ftp (although I wonder if that can be changed in the settings... I've not looked...) When just adding a new site in the Site Manager there is just a dropdown and you don't have to type sftp://

Just to say, I just tried installing WordPress Importer again on a new install and this time it worked fine, so whatever the problem was seems to have been resolved. @girish I think this can be marked as solved (it's too old for me to edit, turn into a question and mark solved myself).