itonstandby

Just a theory, but perhaps the 2018 theme will be released when Gutenberg becomes official. It’s pretty likely we’ll see that release this year and it would be kind of awkward to have a pre and post Gutenberg 2018 theme. Just my two cents.

Perhaps the site is not correctly configured to redirect the non-www URL to the www URL. If the EMR plugin is not installed does the web address redirect properly?

Awesome! I’m looking forward to it.

All in One WP Security & FIrewall, or AIOWSF for short, is the go to security plugin we use on all our sites and our client sites. It is by far the most stable I’ve found and I’ve tried just about everything.

Sunliwilliams, your statement “yet Elegant Themes still chose to be constrained by the GPL” is not really accurate nor fair. If anyone wants to create products for WordPress, the most popular CMS by far and the foundation of almost a fourth of all websites in the world, the GPL is a required beast.

Is it legal what LP did? By all accounts it appears so. But that doesn’t make it any less palatable just because it’s legal.

If a man in his 40’s starts dating my 19 year old daughter, technically it’s legal (in the US) because she’s over 18. But, that doesn’t make it any less of an insult. And it certainly doesn’t take away my right as her father to cry foul. Nor for others to agree with me that the older guy is suspect.

I just replied to another support entry here regarding the same thing and recommended using the WordPress default in General Options > Email Configuration.

Is that the best option right now?

[edit] I changed my responses in the other thread and referenced the link above where the issue is being tracked.

The S2Member lead developer has referenced the link below as the place to keep up with the status of this topic

https://github.com/websharks/s2member/issues/689

This issue is also being asked in another post

https://www.ads-software.com/support/topic/new-user-email-message-password-now-always-set-to-both?replies=5

I’m getting the problem on a test site. It seems the problem occurs after a long period of inactivity. It only happens in Chrome, however. Safari is just fine. Obviously, I’m using a Mac.

Other than deleting cookies in the browser, the only solution is to deactivate, delete, and reinstall iThemes Security.

I have no site cache in place. I cannot continue with this issue so I will be changing to another plugin for security.

Just a note – on the detail page for a product (Divi+new Woo) the description is present in the code but there’s a “display:none” style that’s keeping it from showing. This can be seen with Chrome’s Inspect Element feature and probably Firebug and others too.

Not sure what to do about it at this point, but that’s one problem confirmed.

Just out of curiosity, why do you want to use Access to open the database? What do you hope to achieve?

If you need to browse the database, it is possible to use phpMyAdmin at your web host.

Has any further consideration been given to this feature?

It has been a part of better-wp-security for a long time and I completely overlooked its absence in AIOWSF until now.

If anyone is interested, the commands we use in the shell script to check permissions are below. (loginname should be the cPanel login name)

find /home/loginname/public_html -type f -perm 555
and
find /home/loginname/public_html -type d -perm 555

We also check within all php files for the presence of “0555” which should probably never be in a WordPress php script.

find /home/loginname/public_html -name *.php -exec grep "0555" '{}' \;

Note the above commands do not fix the issues, but merely detect. Since they are in a cron job the output of the commands is delivered by email.

The image hotlink prevention setting in AIOWSF version 3.9.0 is causing the broken image link behavior now on several of our sites regardless of theme and other components. WordPress v4.1.1

Might want to give it a test in your lab. We’re unchecking it for now.

Strangely, the issue seems to have disappeared. Two different sites that were previously exhibiting the behavior – now all fine. I’ll keep vigilant about it and update this thread if anything changes.

Also, where do I submit feature requests for AIOWPSF? Is this forum sufficient or is there a preferred method?