DLJones

I have updated to the latest versions of the MailPoet plugin, emptied cache. I have re-verified my key and it is says:
“Your key is valid
MailPoet Sending Service is active
MailPoet Premium is active”

BUT, when I go to the email I want to send, I see this message in red:
“You’ll soon be able to send once our team reviews your account. In the meantime, you can send previews to your authorized emails.”

Please…how can I resolve this issue???

Just wondering if there is a solution for the issue with tag pages noted above…?

I have just reviewed this thread from five months ago. Today, I see that the List view is still not working on my Tag pages. You can see an example here:
https://www.cod.blueorchard.ca/test-tag/on-sale/

It looks like a solution to this problem was provided above. I’m wondering if/when it will be integrated into the plugin? I would really like the List View default to work on my Tags page ??

Thanks so much–I really appreciate your plugin!
Deborah

I have just reviewed this thread from five months ago. Today, I see that the List view is still not working on my Tag pages. You can see an example here:
https://www.cod.blueorchard.ca/test-tag/sale/

It looks like a solution to this problem was provided above. I’m wondering if/when it will be integrated into the plugin? I would really like the List View default to work on my Tags page ??

Thanks so much–I really appreciate your plugin!
Deborah

I received the help I needed. Issue resolved – thank you!

That’s great, thank you so much, I look forward to hearing from you by email!

Does the subscription confirmation go to the MailPoet plugin “default sender” email or does it go to the mail email address specified in the WordPress General Settings? Since I am helping run client websites, the MailPoet default sender email typically belongs to the client (but I asked them and they have not received the confirmation request emails) whereas the main email in the WordPress General Settings is my business email: [email protected]

Thanks so much for your help!
Deb

Wow, thank you very much! Your advice has been very helpful. I was suspicious of my iThemes Security plugin and, apparently, for good reason:

When I log in via FTP and put a 1 at the end of the folder name for that plugin, I can see my login page again. BUT, I still can’t successfully log in. When I enter my username and password and press Log In, then I get the fatal error message again.

So, I think my best option is likely to follow up with the iThemes Security plugin Support Team!

In the meantime, my client’s website is still up and running so, really, it could be far worse!

Thank you again for your advice–I appreciate your help and wish you a great weekend!
Deb

Hi Brett, thanks so much for your quick response! The actual website (https://www.southernstone.ca/) is fine. But, I receive the error when I attempt to log into the WordPress Control Panel.

I am able to access the site via FTP (I downloaded the readme.html file to confirm the WordPress version).

I have am mildy uncomfortable working in PHP but am willing to give it a go!

David and Davor, thank you so much for your help and considerate suggestions. I am embarrassed to tell you the issue…but at least it is resolved. When I moved the site, somehow the .htaccess file was renamed without the period…and I didn’t notice it was missing until a moment ago. Period put back, login page magically appears. Sigh, that was a lot of stress for such a little punctuation mark. I’m so sorry to have used your time. I really appreciated it!
Deb

Hi David, I renamed the .htaccess file so it is not longer in play. So, is what is inside it relevant? Here is what it contained. Is it possible for an .htaccess file to “cache” at the server level so it is in play even though I renamed it?

# BEGIN iThemes Security
# BEGIN Hide Backend
# Rules to hide the dashboard
RewriteRule ^(/newsite/)?isoexpertin/?$ /newsite/wp-login.php [QSA,L]

# END Hide Backend
# BEGIN Tweaks
# Rules to block access to WordPress specific files
<files .htaccess>
Order allow,deny
Deny from all
</files>
<files readme.html>
Order allow,deny
Deny from all
</files>
<files readme.txt>
Order allow,deny
Deny from all
</files>
<files install.php>
Order allow,deny
Deny from all
</files>
<files wp-config.php>
Order allow,deny
Deny from all
</files>

# Rules to disable directory browsing
Options -Indexes

<IfModule mod_rewrite.c>
RewriteEngine On

# Rules to protect wp-includes
RewriteRule ^wp-admin/includes/ – [F]
RewriteRule !^wp-includes/ – [S=3]
RewriteCond %{SCRIPT_FILENAME} !^(.*)wp-includes/ms-files.php
RewriteRule ^wp-includes/[^/]+\.php$ – [F]
RewriteRule ^wp-includes/js/tinymce/langs/.+\.php – [F]
RewriteRule ^wp-includes/theme-compat/ – [F]

# Rules to prevent php execution in uploads
RewriteRule ^(.*)/uploads/(.*).php(.?) – [F]

# Rules to block unneeded HTTP methods
RewriteCond %{REQUEST_METHOD} ^(TRACE|DELETE|TRACK) [NC]
RewriteRule ^(.*)$ – [F]

# Rules to block suspicious URIs
RewriteCond %{QUERY_STRING} \.\.\/ [NC,OR]
RewriteCond %{QUERY_STRING} ^.*\.(bash|git|hg|log|svn|swp|cvs) [NC,OR]
RewriteCond %{QUERY_STRING} etc/passwd [NC,OR]
RewriteCond %{QUERY_STRING} boot\.ini [NC,OR]
RewriteCond %{QUERY_STRING} ftp\: [NC,OR]
RewriteCond %{QUERY_STRING} http\: [NC,OR]
RewriteCond %{QUERY_STRING} https\: [NC,OR]
RewriteCond %{QUERY_STRING} (\<|%3C).*script.*(\>|%3E) [NC,OR]
RewriteCond %{QUERY_STRING} mosConfig_[a-zA-Z_]{1,21}(=|%3D) [NC,OR]
RewriteCond %{QUERY_STRING} base64_encode.*\(.*\) [NC,OR]
RewriteCond %{QUERY_STRING} ^.*(%24&x).* [NC,OR]
RewriteCond %{QUERY_STRING} ^.*(127\.0).* [NC,OR]
RewriteCond %{QUERY_STRING} ^.*(globals|encode|localhost|loopback).* [NC,OR]
RewriteCond %{QUERY_STRING} ^.*(request|concat|insert|union|declare).* [NC]
RewriteCond %{QUERY_STRING} !^loggedout=true
RewriteCond %{QUERY_STRING} !^action=jetpack-sso
RewriteCond %{QUERY_STRING} !^action=rp
RewriteCond %{HTTP_COOKIE} !^.*wordpress_logged_in_.*$
RewriteCond %{HTTP_REFERER} !^https://maps\.googleapis\.com(.*)$
RewriteRule ^(.*)$ – [F]
</IfModule>
# END Tweaks
# END iThemes Security
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /newsite/
RewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /newsite/index.php [L]
</IfModule>

# END WordPress

Hi David and Davor, thanks so much for your responses! I have reviewed the instructions for properly moving a WordPress website within my own site and I followed them correctly.

I have renamed the .htaccess file but I still cannot get to the login page.

When I try to access these links, I get redirected to a page with the following error. Even though I can verify that these files are indeed sitting on the server where they should be:

These links:
https://www.cmacinc.ca/wp-login.php
https://www.cmacinc.ca/wp-admin

Redirect to:
https://www.cmacinc.ca/not_found
“Not Found
The requested URL /not_found was not found on this server.
Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.”