tbennett04

Oh man https://www.ads-software.com/support/topic/mass-messaging-page-not-accessible?replies=6

very helpful thank you lordkhaoz

Wow okay. This plugin doesn’t work at all for me then… I get a 404 at the mass messaging page [domain]/members/thomasbennett/messages/

When I go into the admin I also see a Stormation tab that wants me to log in…

[domain]/wp-admin/admin.php?page=Stormation

Public. You just type the name and it appears? Hmmm…. :-/

You should be able to in your control panel from your hosting provider. Look for PHPMyAdmin and you can export a copy of your entire database, or just that particular table.

You can probably find a plugin to back up the database as well.

I moved this from under Settings to Posts.

If you edit randomtext_admin.php on line 8 change add_options_page to add_posts_page then it moves it from under settings to under posts.

This would cause upgrade problems if you tried to upgrade the plugin but its a more logical spot for this, imo.

You want to put PHP in your database that executes?

Its in the database under the randomtext table.

I’m up-to-date but am still experiencing it. Did you do any changes to your server? Note, this works locally but not on my server.

Did you ever figure this out? I’m having the same issue…

looks like you are right. comments retracted! this must be a permalink setting with custom permalinks

what are you trying to achieve with lines 1 and 2? that looks like the culprit… i’m no . .htaccess guru but a 301 is a redirect

you can’t put a variable inside that string

it should look like this

$myposts = get_posts(array('numberposts' => '10', 'offset' => '0', 'category' => $cat))

What did you update to get this error? In the meantime create a page and put it in the root directory called index.html and let it say the site is down for maintenance and will be back up soon. You DONT want your client or their clients seeing this!

Why can’t you just reinstall it?

Do you have any redirects in your htaccess file? Are you using plugins that may be causing this? Try disabling them to see. If it correct, reenable 1 by 1. This is not normal behavior.