• Resolved debncgal

    (@debncgal)


    I’ve activated the WP Security Scan plugin. It recommends changing the wp_ prefix and mentions the lack of a .htaccess file in the wp-admin/ folder. I’m anxious about messing up the wp_ prefix change process, so a little more specificity would help me out:

    1) Will changing the wp-config.php file permissions to “666” meet the needed requirement?

    2) Please clarify what is meant by making sure the database has “ALTER rights.” How do I check for that? What am I looking for?

    3) As far as the plugin’s observation that I don’t have a .htacess file in the wp-admin folder, what code should that .htaccess file contain?

    4) Is there anything else I need to do before implementing the wp_prefix change?

    I really want to complete these security measures, but I just need a little more info. Thank you in advance for any help.

Viewing 3 replies - 16 through 18 (of 18 total)
  • I took the precaution to modify only the table names. Instead of replacing all occurences of ‘wp_’ with ‘prefix_’. I choose to replace ‘wp_comments’ with ‘prefix_comments’, ‘wp_links’ with ‘prefix_links’ etc.

    After the update of the database I fixed the “You do not have sufficient permissions to access this page”.

    Thread Starter debncgal

    (@debncgal)

    Well, after a few hacks, I decided it was time to get around to changing my wp_ prefix!

    jmodjeska, your instructions were extremely helpful. Your fallbacks removed much of my anxiety over the process. Surprisingly to me, I did not experience the insufficient permissions problem.

    Thank you so much for taking the time to lay out such detailed step-by-step procedures. Once I read through your instructions, I felt confident in tackling something I’ve been avoiding for quite some time.

    All the best,
    Deb Phillips

Viewing 3 replies - 16 through 18 (of 18 total)
  • The topic ‘[Plugin: WP Security Scan] Anxious About Changing wp_ Prefix’ is closed to new replies.