Dzynit

I don’t see an email from you yet. I had mis-typed heather at first, but edited the post right away. Could you double check that you sent it to heather (at) searchcommander.com please? Let me know what email address your sending from too just in case it might pop into my spam folder.

Thanks, Heather

global $smarty; shouldn’t be printing to the screen, so will you try one more thing for me?

Move the global $smarty; down to the line 143. This will be right before this piece of code:

/******************************************/

	$smarty->assign('extend_header', '
		<script src="themes/' . $settings['app']['theme'] . '/js/seoinspector.js" type="text/javascript"></script>
	');

If that still doesn’t work, would you allow me access to trouble shoot? I’ve not been able to duplicate the error anywhere yet, so I need to see things on a site that it is showing. I would need both a wp-admin login and also ftp to troubleshoot, but please don’t post that in here. You can send to heather (at) searchcommander.com

Using the */pagename worked for me also.

@rootside, I’m wondering if it could be the wordpress seo plugin causing this since it does it’s own rewriting on top of the permalink settings. I was having trouble hiding on a post which if going only by permalinks settings would be category/announcements/pagename – but with wordpress seo active, viewing the page rewrites to just pagename.

Following the path in the error you saw: /wp-content/plugins/seo-automatic-seo-tools/index.php
Add global $smarty; to the beginning of that index.php file. We’ll be releasing a new SEO Tools version in the near future, to deal with this issue.
I thank AllenPayne for pinpointing the fix. I needed to do a little research on the problem and get a confirmation that it was not a plugin conflict before implementing.

Thanks and let us know if that corrects the problem.
Heather

Core Tweaks will just set the permalinks for you if the htaccess file is writable from a single page where you can bulk set most of your wordpress settings at one time. Which is mostly meant for new installs.

You’re likely right cupboy2013, that the rewrite rules have been removed. Did you try just setting the permalinks again? Set them back to a default setting once then set back to your preferred setting. If they’re still not working, do you have ftp access to check the htaccess file to see if the rewrite rules are being added?

Otherwise, you might need to put in a support ticket with your hosting to get help with it. Some IIS hosting will not work with the permalinks not using the index.php in the url. But if they were working before, you should be able to set the reset the rewrite rules to have them start working again.

If you’re comfortable editing in the database, the same solution from matthiaswh will work for you. The date-based is in the same place in the wp_options table and it’s right after the disable-author part.

Even with the latest plugin version, I still have to edit the setting directly in the wp_options database table as matthiaswh described above. I’ve not found any other work-arounds if you don’t have access to edit the database.

The headers already sent message is most commonly a plugin conflict or when the plugin files corrupted during installation. I occasionally have a problem where the plugin files didn’t fully unpack and install correctly because the server had suddenly gone down at the time of installation.

Scott’s suggestions are best to try first. Deactivate seo tools, fully delete it and try installing it fresh first to see if there was a corruption during installation. If the error persists, as tedious as it may be – turning off all your active plugins, activate seo tools first, and one by one reactivate all your others, each time testing a new plugin search to see when you get that second error.

Since it really wouldn’t take much time, if you want to send me a zip of only your active plugins, I can put them on a test site simply to confirm it being the plugins and not a possible server configuration. I don’t currently have available time to test for which plugin is the conflict, but can at least help to confirm that it definitely is a conflict. You can send the zip to heather(at)searchcommander.com if you want me to do that.

I just updated from 3.0.4 to the latest 3.0.6 and the settings were still there and correct. I don’t have a site with prior to 3.0.4 now though to test jumping to 3.0.6.

philipjohn, if you would try one of yours if they’re still below 3.0.4 and post back on if the settings saved, it could be helpful for this post.

When you says “settings” are you referring to the import/export settings? Or the additional plugins that were included? (The four in the second section of the settings page.)
Those four plugins are being removed because they are becoming out-dated and their features are now built-in to wordpress. They will continue to work if you had them on before upgrading, but can no longer be turned “on” if they were not already on. They can only be turned “off”.

I will bring it to attention on updating the video also.

Just upgraded another 2.1.17 to the latest version and again all the s3 settings were gone.

The same thing happened to me. But I also see a new dropdown box with different S3 locations now. I assume this is an improvement for people that might have one of those different locations rather than the default US Standard location.
If the plugin author could confirm on this please? And it “is” very frustrating to have to re-enter all the info on all the sites it’s in use on. Wouldn’t it be possible to prefill all that with the original default location (if it’s not already been upgraded to this version and changed) and keep the keys and bucket info we’ve put in prior?

Is post teaser still active if you deactivate core tweaks?

Can you try deactivating core tweaks for a few minutes and see if the links are gone? If not, any chance you’re running a cache plugin?
If they do remove, try running core tweaks again remembering to de-select all the settings first, then “add” the links. The run again the same way using “remove” to see if there might have been a glitch in saving the settings in the database initially.

Jeff,
It was taking too long to get this resolved in our situation so we moved on to using: https://www.ads-software.com/extend/plugins/wp-members/

It has everything we needed built-in without having to customize the plugin itself. The thank you page, captcha, full control over notices, etc. The only thing to remember is when you install it on a WPMU site, you need to activate it individually on each network site you want to use it on rather than use the network activate. When first activated, it adds all the initial information for the plugin to the correct network site – so network activate doesn’t add that info correctly.