sab

Hi @photovoltaik1 On my production websites I do the following

1. Switch WordPress Core to get only the security updates automatically and no major version upgrades.
2. Disable Automatic Theme and Plugin Updates. Use a changelog monitoring tool like Visualping.io to monitor the plugin and theme changelogs to get notified when there is an update available. I normally update immediately if it’s a security update or else delay it for a few weeks until I test the updates locally on a staging environment before pushing the updates on the production site to make sure there are no sudden surprises. This has worked for me so far with very few incidents in a calendar year.

Hope this helps.

Hi @junior466 Here are a few things you might try.

1. Create a info.php file in your server with the following file contents <?php phpinfo(); ?> Then open that file and search for the upload_max_filesize and the post_max_size directives and check whether they are set to 128M. If not make try to set both post_max_size=128M and upload_max_filesize=128M in your php.ini file.
2. Make sure you have restarted Apache / PHP-FPM based on your setup. If your setup uses Apache with mod_php restart/reload apache for the changes to take effect. If your setup is Apache with PHP-FPM then restart PHP-FPM for the changes to take effect.

That should hopefully make the changes live. Once you can confirm that, next check the WordPress settings page, which should show the correct settings. Hope this helps.

Thank you for answering my questions @qtwrk

Hi @qtwrk Thank you so much. I had one additional question I wanted to ask.

I have the following Image Thumbnail Group Sizes listed

et-pb-post-main-image ( 400px x 250px )
et-pb-post-main-image-fullwidth ( 1080px x 675px )
et-pb-portfolio-image ( 400px x 284px )
et-pb-portfolio-module-image ( 510px x 382px )
et-pb-portfolio-image-single ( 1080px x 9999px )
et-pb-gallery-module-image-portrait ( 400px x 516px )
et-pb-post-main-image-fullwidth-large ( 2880px x 1800px )
et-pb-image–responsive–desktop ( 1280px x 720px )
et-pb-image–responsive–tablet ( 980px x 551px )
et-pb-image–responsive–phone ( 480px x 270px )`

Of the ones listed, I do not require the following

et-pb-portfolio-image ( 400px x 284px )
et-pb-portfolio-module-image ( 510px x 382px )
et-pb-portfolio-image-single ( 1080px x 9999px )

Does de-regsitering the following sizes, reduce the number of image groups that is submitted to LSCache, and in effect reduce the disk space?

Hi @honyakuservicesllp I cannot help you with the code. I can tell you this much, if the mailer’s don’t work that would mean your WordPress installation does not have working mail functionality. Before you go out and start looking at your code, first try and confirm whether the core WordPress installation can send outgoing emails. If WP-Mail SMTP test mail shows an error when sending a test mail then your configuration is incorrrect in SMTP Mail Settings. If you can provide a log of the error that was produced by WP Mail SMTP when you tried connecting with Other SMTP, I might be able to help you troubleshooting what went wrong.

@honyakuservicesllp one other thing I missed is you also have to configure your SMTP Relay in GSuite.

Follow the instructions from Step 1

https://support.google.com/a/answer/2956491?hl=en

Make sure the following is selected

• Only addresses in my domains
• Require SMTP Authentication option is enabled

Hi @tedor2 most probably this is happening because the database is already selected on the left hand site. Can you try writing only this line in the query editor and kindly make sure the database storylab_db-dub3 is selected on the left hand side in phpmyadmin.

SELECT * FROM wp_posts WHERE post_name='about';

Hi @honyakuservicesllp I am going to put out a list of steps which should help you set up your form email. I am assuming the following based on your domain’s MX records

• Your are using Google Gsuite
• The email id [email protected] exists in your GSuite Account

In order to configure WP Mail SMTP do the following

1> Change your mailer to Other SMTP
2> Select your SMTP host as smtp-relay.gmail.com
3> Set Encryption to TLS
4> Set SMTP Port to 587
5> Turn Authentication on and enter your username [email protected] in SMTP Username field
6> If you have 2 step authentication enabled on the account [email protected], generate an app password and enter that password in SMTP Password field in WP Mailer SMTP
How to generate an app password?
7> Specify the “From email” field as [email protected] in WP Mailer SMTP
8> Save your settings and then send an test email using the test email option.
9> If after doing all the steps mentioned above you still are not receiving a test email in your inbox, then check with your hosting provider to see if SMTP Restrictions are enabled and are in place. They will whitelist your cpanel account and hopefully then it will work.

Hope this helps.

Hi @diondesigns @theoff Thanks for pointing that out. I was absolutely wrong with the Apache Directory directive. The correct Apache code would be

Options -Indexes

as already pointed out by @diondesigns.

Adding this to your .htaccess file should give a 403 Forbidden Error across all the directories. My assumption was my mistake. You can only add Directory directives only in the Apache server configuration files.

@nokaokan This plugin by Jeff Star will disable lazy loading throughout your website

https://www.ads-software.com/plugins/disable-lazy-loading

If you want to do it on a per image basis, look at the post here for more information

https://make.www.ads-software.com/core/2020/07/14/lazy-loading-images-in-5-5/

Hi @tararobertson the url you mentioned redirects to the insecure version of the same about us page which is most probably creating a redirect loop. This is a 301 Redirect that is being generated when you are trying to open this URL which is causing the problem. Remove the direct and the problem should go away.

https://www.gatewaystorage.co.nz/about-us/

Here is an output of the curl command which shows the problem. Look at the location header where the url is redirecting to

 curl --head https://www.gatewaystorage.co.nz/about-us/

HTTP/1.1 301 Moved Permanently
Date: Mon, 12 Jul 2021 11:25:48 GMT
Server: Apache/2.4.48 (cPanel) OpenSSL/1.1.1k mod_bwlimited/1.4
X-Powered-By: PHP/7.4.20
Vary: Accept-Encoding,Cookie
Location: https://www.gatewaystorage.co.nz/about-us/
Content-Type: text/html; charset=UTF-8

Hope this helps.

Hi @urchman89 as I can see you are hosted in hostgator and have access to a cpanel account most probably, you would have the option to change the php version inside your cpanel account. Change your php version from inside your cpanel using “select php version”, you will then get access to your wordpress login page.

Hi @9748076617-1 try including this

<video class="video" autoplay muted loop playsinline>

This might work.

@urchman89 this would most probably mean you may be are running PHP 5.6.38. Trying changing your PHP version to v7.3 or v7.4.

You can check the version you are running by creating a file with any name for example phpinfo.php. Put this code in the page and then open it in your browser. It should let you know what version you are running.

<?php
phpinfo();
?>

Hope this helps.

Hi @theoff it is really not that hard. All you want to do is have this in your .htaccess file

<Directory "/home/your/website/location">
Options -Indexes
</Directory> 

On the Directory line specify the address to your wordpress directory. This will give a forbidden error to all folders under you root wordpress directory including wp-content/uploads/. You really want this because you don’t want the hassle of creating so many index.html files in every folder that you do not want to display. This protects every folder. I am assuming that you are using Apache Web Server. If the server in question is Litespeed then the code would be as follows

Options -Indexes

As far explaining this goes let me try. The Options -Indexes will return a 403 forbidden error if a URL which maps to a directory is requested and there is no DirectoryIndex (for example index.html) in that directory.

If you wanted to know more this is where you should look.
https://httpd.apache.org/docs/2.4/mod/core.html#options