[URGENT] Corrupting WP-Config File

@sophywpress

… as this is a custom prefix we had entered.

What prefix and where did you enter that ?

The standard database tables are wp_ yes?

We entered the custom prefix when we performed a site transfer across to the live servers.

@sophywpress

Right, indeed standard database table prefix is wp_

So you changed that to dps_ using the iTSec plugin Change Database Table Prefix module or using another plugin ?

If using another plugin which one ?

Are you using the InfiniteWP plugin ?

(Even if not using the InfiniteWP plugin) Open the better-wp-security/core/modules/global/settings-page.php file and then search for the string infinite which will take you to a relevant piece of code that looks like this:

<?php if ( is_dir( WP_PLUGIN_DIR . '/iwp-client' ) ) : ?>
	<tr>
		<th scope="row"><label for="itsec-global-infinitewp_compatibility"><?php _e( 'Add InfiniteWP Compatibility', 'better-wp-security' ); ?></label></th>
		<td>
			<?php $form->add_checkbox( 'infinitewp_compatibility' ); ?>
			<label for="itsec-global-infinitewp_compatibility"><?php _e( 'Enable InfiniteWP Compatibility', 'better-wp-security' ); ?></label>
			<p class="description"><?php printf( __( 'Turning this feature on will enable compatibility with <a href="%s" target="_blank" rel="noopener noreferrer">InfiniteWP</a>. Do not turn it on unless you use the InfiniteWP service.', 'better-wp-security' ), 'https://infinitewp.com' ); ?></p>
		</td>
	</tr>
<?php endif; ?>

Is the code using infinitewp_compatibility or infinitedps_compatibility as an argument for the $form->add_checkbox() call ?

Would it be possible to provide a screenshot of the error you are getting when trying to save the settings in the Global Settings module ? I simply need to see how that looks like.

Lots of questions but very little info which makes it hard to debug your issue.

Work with me and we’ll get there … ??

Edit: Single site or Multisite ?

• This reply was modified 7 years, 11 months ago by pronl. Reason: Added an additional question

Hi, no problem I can provide more information for you.

I performed the site restoration with Akeeba backup and Kickstart.

I changed the table prefix in the Kickstart process.

I’ve attached a screenshot of the code, and strangely it isn’t showing the dps prefix, instead the wp prefix.

Should I change it to the dps prefix?

It’s a single site, and if the image doesn’t show open it in a new tab

@sophywpress

No, don’t make any changes to the code.

Next we’ll need to check the html code of the Global Settings page in the browser. I’ll share some new instructions tomorrow.

Hello, do you have the instructions?

@sophywpress

I noticed 2 questions were left unanswered:

Are you using the InfiniteWP plugin ?

Would it be possible to provide a screenshot of the error you are getting when trying to save the settings in the Global Settings module ? I simply need to see how that looks like.

Please answer these questions before we continue.

Hi Pronl,

No I am not using the InfiniteWP Plugin, and here is the screenshot of the error that I am getting.

@sophywpress

Hmm, interesting to see that the error is displayed twice.

Ok, so you are not using the InfiniteWP plugin. Let’s see what happens when we make the plugin think that the InfiniteWP plugin is installed.
Simply create a iwp-client subfolder in the wp-content/plugins folder. No need to put anything in the folder. The fact that the folder exists will make the iTSec plugin think that the InfiniteWP plugin is installed.

Note this is a perfectly safe change to make in your WordPress env. And it can easily be undone. So it’s temporary and nothing serious.

If you now open the Global Settings module and scroll all the way down to the Allow Data Tracking setting you will notice that a new setting is displayed above it, Add InfiniteWP Compatibility.

Now open up the browsers inspector and navigate in the html document tree to the html element that represents the Add InfiniteWP Compatibility setting. I’ve included an example of how this looks like in the FireFox inspector.

Check the value of the name attribute in the checkbox input element with id=”itsec-global-infinitewp_compatibility”. It should say: global[infinitewp_compatibility]
Please confirm it matches this value.

There is another input element (hidden) right below which is supposed to have the same value in the value attribute. Please confirm or even better provide a screenshot so I can verify this.

Now simply enable the Add InfiniteWP Compatibility setting and disable the Write to Files setting at the top of the Global Settings screen and try to Save Settings. Let’s see what result we get.

• This reply was modified 7 years, 11 months ago by pronl. Reason: Changed the last instruction since it was missing something

Hi Pronl,

Thanks for those instructions, I did what you said and unfortunately we receive the same error, below are the attached screenshots which verify that they match to what you said and the error we get after your final instruction.

@sophywpress

Ok, I didn’t actually expect these instructions to solve the issue.
We are just poking around …

But the result does make me think this might be a javascript/ajax issue.
And that is pretty hard to debug remotely…

Tried understanding what happens when clicking on the Save Settings button, but there is a LOT happening. Impossible to figure out where the infinitewp_compatibility is changed into infinitedps_compatibility without being able to debug in the env.

Anyway I’m pretty convinced this is a conflict with something else in the env.

Hi Pronl,

Okay, so what do you think I should do?

@sophywpress

Please provide me with a list of installed and activated plugins in this env.

If this is a conflict with another plugin, deactivating plugins one by one should help us identify which one is causing the issue.

But before we do that I’d first like to see the list of installed and activated plugins.

If we manage to identify the conflicting plugin you could temporarily deactivate it. Then do whatever you need to do in the iTSec plugin (eg disable the Write to Files setting and then click on the Save Settings button).
And then finally reactivate the conflicting plugin.

This would at least provide you with a workaround.

Parallel you could then file a bug with iThemes. Provide them with as much info as possible and then hope they will fix the conflict (or work with the author of the conflicting plugin to resolve the issue).

@sophywpress

There is another workaround option.

Remember you told me:

I changed the table prefix in the Kickstart process.

Suppose you don’t change the table prefix in the Kickstart process.
(Not sure whether this is actually feasible).

The iTSec plugin also includes a feature to change the Database table prefix.
The only difference (probably) is that the iTSec plugin does not allow you to choose the prefix. It’s an automatically generated random prefix.