Solution

• In the setting of the plugin, choose the tab Additional Firewall Rules
• Uncheck the option at the bottom, i.e. Advanced Character String Filter

Config

• WordPress 5.3
• All In One WP Security v4.4.2
• MathJax-LaTex v1.3.11

The post MathJax Load Failed – WP Security Plugin appeared first on LarryLai.

Background

After installing WP Health, it’s shown that both MariaDB 5 (a default replacement of MySQL for CentOS7) and PHP5.6 are obsolete, i.e. no more formal support and no security patches will be released. It’s suggested to upgrade at least to MariaDB10 and PHP7.

Apart from security and support concern, it’s known that PHP7 has better performance than PHP5.

Issue

After upgrading, either the Virtualmin has problem in displaying submenu on the left panel or there’re “Internal Server Error” on some WordPress sites. It’s found out that during yum update MariaDB, it’s required to remove the old MariaDB5, however, for packages dependency needs, yum will at the same time remove Postfix and Virtualmin-base. If these 2 packages are reinstalled after upgrading to MariaDB, then WordPress has problem.

Solution

Use rpm -e –nodeps to skip removal of Postfix and Virtualmin-base.

Tricks

After removal PHP5.6, list out all the related packages, e.g. php-mysqlnd, php-gd, etc. depending on my case, there’re some others. All these have to be reinstalled after installing PHP7.2 base package.

For upgrade of PHP7, never upgrade to the lastest PHP7.3 as some of the PHP packages do not have PHP7.3 compatible rpm, only have PHP7.2 compatible rpm. There’re many CentOS PHP7 upgrade info. on the web, but some are not good, after try and error, I use TecAdmin.net’s advice and got no problem.

Config

• CentOS: 7.6
• Virtualmin 6.06
• WordPress 5.1
• MariaDB: 10.1

The post Centos7 Virtualmin Upgrade PHP7 MariaDB appeared first on LarryLai.

During scanning stage of running the Duplicator plugin on a WordPress site, there was an error: Server Error 500.

Solution:

Modify /etc/php.ini file to increase memory:

memory_limit = 256M

from 128M

Tricks:

Even there is error during the scanning stage, Duplicator still allowed building step to proceed and showing no error.

Error 500 actually does not tell anything informative

No special message was logged in Apache web server

Config:

• PHP               5.6.30
• WordPress     4.7.4
• Duplicator     1.2.4

The post WordPress Duplicator Plugin Server Error 500 appeared first on LarryLai.

After installing WP Fastest Cache plugin, whenever update any plugin, there is error – Update failed. Could not remove old plugin.

Solution:

1. Go to WPFC at the top bar
2. Delete Cache and Minified CSS/JS
3. Update the plugin that needs to be updated

Tricks:

In case after installing WP Fastest Cache for quite a while, then there is need to update any other plugin and you found error. It is difficult for us to remember it should be the WPFC goes wrong.

The performance of this plugin for page access speed for my case is even better than other caching plugin like WP 3C Total Cache

Config:

• WordPress    4.7.3
• WP Fastest Cache     0.8.6.7

The post WP Fastest Cache Plugins Update Issue appeared first on LarryLai.

When moving some of the content to a single page design, the menu link will be addressing the div id instead of another page. But after all set up perfectly, the menu item link to the correct anchor, but missed to locate the correct position of the section, i.e. the anchor, div id.

Solution:

Using a WordPress plugin: Page Scroll to id and tuned the delay for scrolling setting

Tricks:

Better starts with a larger no. of delay and fine tune it to a smaller but large enough time delay for the page to run other scripts. In my case, heavy rendering for the Math symbol by MathJax may cause the missing position issue.

Config:

• WordPress     4.7.2
• Themify Theme Shoppe  1.0.2
• Page Scroll to id:  1.6.2

The post Scrolling to Section ID Missing appeared first on LarryLai.

error: “Sorry, no products matched your selection. Please choose a different combination.”
WooCommerce in WordPress shows all variations of variable product including unmatched variations thus the above error message may occur. But it used to be working fine. Perhaps, the error occurred after a WooCommerce update.

Solution:

Update php version from 5.4 to 5.6. Since php version 5.6 is not in the official repository of CentOS 7 as of Jan 2016, follow this thread on CentOS to install php56u works fine.

Tricks:

1. Click on System Status under WooCommerce plugin. There is a warning on php version under Server Environment stating that php 5.6 or above is required, … php5.4 is running.
2. As of Jan 2016, latest php version in the official repository of CentOS 7 is still the very old php5.4. Thus, 3rd party repository must be considered in order to install php5.6 on CentOS 7.
3. Some advise updating php with Webtatic’s php56w, but CentOS forum states that it is not recommended to use Webtatic repository.
4. After installing/ replacing php5.4 with php56u, some php extensions may not be compatible with the new version. And these extensions have to be updated too. E.g. Imagick has to be updated. If PECL is in place, the following command works fine:

#yum install php56u-pecl-imagick

Config:

• CentOS 7.3
• WordPress 4.7.1
• WooCommerce plugin   2.6.13

The post WooCommerce Showing Unmatched Variations appeared first on LarryLai.

It is quite terrifying if suddenly all the custom CSS disappear and you do not have a backup of the text of the custom CSS that is not just one or two lines, but it is filled with many lines.

Issue:

After updating theme Accelerate to the latest version as suggested by WordPress, all the custom CSS under Appearance admin menu of the child theme was gone.

Solution:

Restore to the original Virtual Machine hosting WordPress to the version just before updating the theme by Mac’s TimeMachine.

Tricks:

• It is supposed that the child theme would not be altered after updating the parent theme. However, I guess (as I’m not a WP framework expertise) that WordPress 4.7 removed the custom CSS option and instead deployed “Additional CSS” option, and put it in another area in the database rather than under the configuration of the theme.
• Before updating the theme version, there was no issue on the prior update of WordPress 4.6.1 to 4.7. But still the issue may not be caused by merely the latest theme version.
• Though TimeMachine can restore previous backup of Virtual Machine, it is more convenient to restore the snapshot of a Virtual Machine if there is a snapshot taking just before starting the theme update. In this case, how do people expect a child theme could be altered by updating the parent theme version?

Config:

• WordPress     4.7
• Theme            Accelerate 1.2.9
• Mac OS X      10.12.2

The post WordPress Custom CSS Disappear appeared first on LarryLai.

“Error: Missing argument to \begin” when using \color command and together with \boxed command in WordPress with MathJax plugin as if they are under LaTex syntax.

Solution:

Adding {} to embrace the content under the \color command. Actually, in LaTex syntax, \color command does not need to use {} as all content after the \color is coloured according to the defined color, e.g. \color{red}. However, for MathJax, you cannot add another LaTex command immediately after \color command, and you need to add {} to embrace the content to be coloured. For example, \color{red}{\boxed{f(x)}}

Config:

• WordPress:         2.6.1
• MathJax plugin:  1.3.4

The post MathJax Incompatibility to LaTex appeared first on LarryLai.

After disabling a website through disabling the virtual server in Virtualmin, then re-enabled the virtual server, there’s error in accessing the website with error log:

AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error. Use ‘LimitInternalRecursion’ to increase the limit if necessary. Use ‘LogLevel debug’ to get a backtrace.

Solution:

1. Back to Virtualmin, select the problem web server
2. Choose Server Configuration -> Website Redirects
3. Delete the URL Path: ^/, and just leave /dav (if exist)

Tricks:

Most forums suggest editing .htaccess file in the root html directory, but it does not help

The main reason for such error is that the permission/ownership of public_html excluded the user of the specific virtual server, in my case, the ownership of the directory was set as “apache:apache”, and it created the problem that virtualmin could not create a file called disabled_by_virtualmin.html. Action point 3 of the Solution above can solve this issue just once, changing the ownership of the directory, public_html to “[web server user]:apache” can cure the issue for good.

Config:

• CentOS        7.2.1511
• Virtualmin    5.04

The post Virtualmin cannot access re-enabled Virtual Server appeared first on LarryLai.

WordPress plugin Tabby Responsive Tabs shows inappropriate border.

Solution:

1. Go to setting of another plugin – Easy Google Fonts,
2. Uncheck Force Styles Override (Optional)

Config:

• WordPress      4.6.1
• plugin: Tabby Responsive Tabs  1.2.3
• plugin: Easy Google Fonts   1.4.1

The post WordPress Plugin: Tabby Responsive Tabs appeared first on LarryLai.