Title: Persistent old settings
Last modified: August 31, 2016

---

# Persistent old settings

 *  [bridieamelia](https://wordpress.org/support/users/bridieamelia/)
 * (@bridieamelia)
 * [10 years, 2 months ago](https://wordpress.org/support/topic/persistent-old-settings/)
 * Hi, I inherited a site that was cloned from another site. We are getting loads
   of 403 errors in Google Webmaster tools, and trying to find why. In options.php
   I found entries for:
 * quickppr_redirects
    quickppr_redirects_meta
 * Even though the plugin wasn’t installed.
 * In our onpage.org account, it seems there are no follows set up on pages, but
   on reinstalling the QPPR plugin, I can see “no follow” is not set in individual
   page settings.
 * Is it possible that old settings persist in the database?
 * I am trying to get access to PHPmyADmin but in the meantime tried the code at:
   
   [https://wordpress.org/support/topic/plugin-quick-pagepost-redirect-plugin-remove-uninstall-clean-database?replies=8](https://wordpress.org/support/topic/plugin-quick-pagepost-redirect-plugin-remove-uninstall-clean-database?replies=8)
 * Which created a PHP error.
    `Parse error: syntax error, unexpected '$sqloptions'(
   T_VARIABLE) in /home/veinoplu/public_html/wp-content/themes/virtue-child/functions.
   php on line 9` Is it possible for you to share updated code? Or shed further 
   light on the problem?
 * TIA
    Bridie
 * [https://wordpress.org/plugins/quick-pagepost-redirect-plugin/](https://wordpress.org/plugins/quick-pagepost-redirect-plugin/)

Viewing 1 replies (of 1 total)

 *  [Don Fischer](https://wordpress.org/support/users/prophecy2040/)
 * (@prophecy2040)
 * [10 years, 2 months ago](https://wordpress.org/support/topic/persistent-old-settings/#post-7136617)
 * Bridie,
    To clarify a few things:
    1. The plugin is designed to cease function when deactivated. This means that if
       it is not turned on (or was turned on and set up previously but is deleted or
       turned off), it will not perform any redirects or function in any way. The ONLY
       exception to this, is if you have caching setup, and then you must clear your
       site cache to clear the cached redirects (this is due to the caching and not
       the plugin).
    2. The plugin has a method in it’s options to remove all database entries when 
       deactivated. So as long as everything is working as it should, you check the
       boxes and save the options, and then turn the plugin off. This should remove
       all the entries in the database.
    3. The thread you are referring to on removing data is over 3 years old and refers
       to a much older version of the plugin. Remove the code from your functions file
       as it is no longer relevant.
    4. Leaving the entries in the database from the previous install will not hurt 
       anything and will not cause any from of ‘rouge’ activity, like unwanted redirects–
       they are just settings and need the plugin to work. At the worst, they just 
       take up a little space in the database and do not hurt anything at all.
 * Without knowing what 403 errors you are getting and without knowing what you 
   have setup on your site (or how it is programmed), it is impossible to say what
   the cause it of the errors. One thing I can say with quite a bit of certainty,
   is that it is most likely NOT the result of the plugin – especially if the plugin
   is off or removed and your cache was cleared (barring you have caching set up).
 * “403” errors are a “Forbidden” notice. This generally means that the page or 
   directory you are trying to access does not have browsing permissions. It sounds
   like you have more of a file or directory permissions issue than anything else.
   The first thing I would do, is check your file/folder permissions for the site
   and make sure they are setup correctly. Additionally, check your permalinks setup
   and reset it if you have not. If you have a bad setup from an outdated .htaccess
   file, that can also cause the 403 errors because the URL does not resolve to 
   the correct or intended place.
 * One last thing to check – If you have folders set up, for example ‘documents’
   and you have a page named ‘documents’ and have the %pagename% permalink structure
   set up, that will cause all requests for that page and subpages to go to that
   folder and look for a file (index.php) in that folder or subfolders. If directory
   browsing it turned off, that would throw a 403 error or a 404 error for anything
   related to the directory.
 * Good luck with the hunt.
    Regards, Don

Viewing 1 replies (of 1 total)

The topic ‘Persistent old settings’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/quick-pagepost-redirect-plugin_8d7b6f.
   svg)
 * [Quick Page/Post Redirect Plugin](https://wordpress.org/plugins/quick-pagepost-redirect-plugin/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/quick-pagepost-redirect-plugin/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/quick-pagepost-redirect-plugin/)
 * [Active Topics](https://wordpress.org/support/plugin/quick-pagepost-redirect-plugin/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/quick-pagepost-redirect-plugin/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/quick-pagepost-redirect-plugin/reviews/)

## Tags

 * [no-follow](https://wordpress.org/support/topic-tag/no-follow/)
 * [phpmyadmin](https://wordpress.org/support/topic-tag/phpmyadmin/)
 * [redirect](https://wordpress.org/support/topic-tag/redirect/)

 * 1 reply
 * 2 participants
 * Last reply from: [Don Fischer](https://wordpress.org/support/users/prophecy2040/)
 * Last activity: [10 years, 2 months ago](https://wordpress.org/support/topic/persistent-old-settings/#post-7136617)
 * Status: not resolved