Vinayy

Dear Steven

Thanks, it worked!

For anyone else wanting to do the same, please note that this has to remain unchanged:

Text domain: connections_hours

Original string: Sorry, we are currently closed.
Text domain: connections_hours
Text context: (leave this empty)
Replacement string: you new text here

Hi @akshay-menariya, you wrote –

I will add this empty check in the next plugin update.

I got this today for a menu with no content.

Sorry, you are not allowed to access this page.

Replacing [ and ] with { and } worked for me. Of course, the plugin needs a proper update.

Open the file: plugins/jetpack/modules/widgets/simple-payments.php

Go to line 220

CHANGE:

			wp_send_json_success( [
				'product_post_id' => $product_post_id,
				'product_post_title' => $params['post_title'],
			] );

TO:

			wp_send_json_success( {
				'product_post_id' => $product_post_id,
				'product_post_title' => $params['post_title'],
			} );

Edit: This merely removed the error but the plugin is not getting activated. The plugin needs an update.

• This reply was modified 6 years, 4 months ago by Vinayy. Reason: Plugin is not throwing the error but it is not getting activated

hmm .. Still no response! ??

Anyway, I deleted all the IPs from Ban Hosts and saved the setting and it resulted in a .htaccess file of 13 KB. Now, this too did not have the other content of the .htaccess file as this time also the .htaccess file got truncated after your last line.

So, this means that the number of IPs or the size of the .htaccess file is not responsible for the file getting truncated. It means that your plugin has a bug.

This ..

# BEGIN iThemes Security - Do not modify or remove this line
.. all your code of IPs ..
# END iThemes Security - Do not modify or remove this line
 
all other default content

Changed to ..

# BEGIN iThemes Security - Do not modify or remove this line
.. all your code except IPs of Ban Hosts..
# END iThemes Security - Do not modify or remove this line
?

It means that your plugin has a bug which deletes everything after your last line.

Can you please do something about this?

Whenever I update IPs in Ban Hosts, WHY is the .htaccess file getting truncated after your last line?

This ..

# BEGIN iThemes Security - Do not modify or remove this line
.. all your code of IPs ..
# END iThemes Security - Do not modify or remove this line
 
all other default content

Changes to ..

# BEGIN iThemes Security - Do not modify or remove this line
.. all your code of IPs ..
# END iThemes Security - Do not modify or remove this line

WHY?

Such a thing wasn’t happening earlier!!

Every time I update the Ban Hosts list, I have to log in through FTP and physically go and update the .htaccess file by copying back the code that iThemes deleted from .htaccess. ??

@edanzer – Yes, the issue has has been fixed.
Thanks!

@edanzer, alright, waiting.

Thanks in advance.

Hi @jdembowski

Oops! I had copied the text, which I had posted elsewhere to mention about Mail Bank (with link) and posted it here as well. ?? I too was wondering if 3 links are allowed. I’ll try and keep this in mind in future.

BTW, I didn’t get your question. Where in the code does it do what?

I guess this is what you wanted to know:

“the plugin” stores the SMTP email password in the WP database after encrypting it, unlike some other similar plugins, which store the password in plain text.

hahaha .. I found Mail Bank better as it encrypts the password before storing it in the database.

Also, in many other SMTP plugins, even if the password shows as hidden (*****), you can still see it using view-source. Whereas in Mail Bank, it shows the password as ***** even when you view the page source.

So, Mail Bank is definitely better.

It stores the password in plain text format even in the database.

Since yesterday I have received 111 large emails about Site Lockout Notification on just 10 websites. Out of these, 50 are of one website and 51 of another one.

Please do something about this at the earliest.

You can provide an option for us to choose between simple formatted emails or the new one.

• This reply was modified 7 years, 11 months ago by Vinayy. Reason: link to screenshot of emails added

Zerif Lite Version: 1.8.5.6 has fixed most of the issues but Parallax effect is still not working.

This could have been avoided. Now I have to go to every WP installation and disable getting such emails.

@sanchr, I reverted to WordPress 4.3.1 and the comments are displaying normally with the [last] setting.

I want to clarify that in both the WordPress versions there was no problem with other pages, which have less than 50 comments.

It means there might be some problem with WordPress 4.4 if a page has a large number of comments.

RESOLVED