LandyVlad

Update OK weirdness.

I looked in the upload folder itself and one of the files which ‘errored’ is actually there but is not showing up in the media linbrary. I had to delete it via cpanel and then upload again through media library (as before) and now it is showing.

No longer having any uploading troubles.

For now.

I am, very confused.

The below is the htaccess file in my public html directory, as it stands now.

 #Begin Really Simple Security
# <IfModule mod_rewrite.c>
# RewriteEngine on
# RewriteCond %{HTTP:X-Forwarded-Proto} !https
# RewriteCond %{REQUEST_URI} !^/\.well-known/acme-challenge/
# RewriteRule ^(.*)$ https://%{HTTP_HOST}/$1 [R=301,L]
# </IfModule>

#End Really Simple Security
# 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
php_value upload_max_filesize 138M
php_value post_max_size 138M
php_value max_execution_time 300
php_value max_input_time 300

# BEGIN LiteSpeed
# The directives (lines) between "BEGIN LiteSpeed" and "END LiteSpeed" are
# dynamically generated, and should only be modified via WordPress filters.
# Any changes to the directives between these markers will be overwritten.
<IfModule Litespeed>
SetEnv noabort 1
</IfModule>
# END LiteSpeed

# php -- BEGIN cPanel-generated handler, do not edit
# Set the “ea-php80” package as the default “PHP” programming language.
<IfModule mime_module>
  AddHandler application/x-httpd-ea-php80 .php .php8 .phtml
</IfModule>
# php -- END cPanel-generated handler, do not edit

as you can see the Really Simple Security code at the top of the file is commented out.

Fixed! I found out by looking at the sample file it needed to be ‘visible’

Success !

OK so I found out that the site is actually hosted somewhere different to what I thought – there were duplicate accounts but only one with the DNS pointing to it.

I’m trying to access that and transfer it to my own hosting to sort this out!

Thanks for your help so far I’ll report back how it finally works out for future reference. 🙂

Sadly no luck.

I have tried all convolutions of the above suggestion.

• (existing) Divi theme, all plugins bar woocommerce enabled.

• Divi theme, all plugins bar woocommerce disabled.

• Storefront theme, all plugins bar woocommerce disabled.

Still exactly the same behaviour as per my original post.

It’s very frustrating for sure – any other ideas?

Could these things have anything to do with it? Perhaps someone can explain them to me? On the face of it, it doesn’t appear to me that either of these would or could cause the issue I am experiencing.

SoapClient: ❌ Your server does not have the SoapClient class enabled - some gateway plugins which use SOAP may not work as expected.

Multibyte String: ❌ Your server does not support the mbstring functions - this is required for better character encoding. Some fallbacks will be used instead for it.

@renehermi

In order to prevent a customer from having access to a staging site while in progress, I would prefer to set it up like this.

They would have an existing website at http://www.customerbusinessname.com

I would develop their new website at (for example) staging1.mywebsite.com

On completion I’d then push the website from staging1.mywebsite.com to be LIVE at http://www.customerbusinessname.com (replacing the existing website completely).

Can WP staging do this? Easily? If so is there info in the documentation about it?

Ta

Thank you

Thanks mate.
yep I know they are cpanel tools, I’ll check with the host per your suggestion.
Cheers