Forum Replies Created

Viewing 15 replies - 61 through 75 (of 102 total)
  • Thread Starter Dzynit

    (@dzynit)

    I never got any help with it so used a different plugin: http://wordpress.org/plugins/postie/

    It has a lot of different options that are useful and you can limit to only certain users of the site or make it fully available to anyone with a wp-admin login. It seemed complicated at first glance, but turned out to be easy to use.

    Looks like you are using minify in a cache plugin. You could try turning that setting off and see if there’s any improvement. I’ve had trouble with that before on sites using seo tools or plugins that are heavy on scripts.

    Another thing you could check on is asking your hosting if there is any blocking going on preventing those external scripts from being able to load. I’ve seen a lot of that lately on different hosting companies.

    Thank you Slobodan. I was really glad to find your solution. It was very helpful and saved a lot of time and frustration.

    To anyone running across this post looking for help with the same problem, I used this: http://slobodanmanic.com/444/flexible-horizontal-sidebars-wordpress-twenty-thirteen-child-theme/

    But you have to download his zip and copy the code because there seems to be some code missing from the snippets that are right in his post.

    In my case it was permission issues on some of the files and folders on the site. Hosting had to correct that for me. Still unsure of what caused the permission problem though because all previous automatic upgrades worked perfectly fine. When this happened, even manual uploading wasn’t working.
    Since your error says permission denied in it, it might be worth putting in a ticket to your hosting and see if that could possibly be your problem too.

    My hosting support initially told me that the upgrade was timing out and wordpress was at fault. But they eventually dealt with taking care of the permission problems on all the files and folders and the upgrade worked correctly. Even plugins were failing to complete upgrade and a single plugin timing out just didn’t seem logical.

    Thread Starter Dzynit

    (@dzynit)

    If you could re-open the other support thread, I can ask the other people having the problem to compare plugins with me to see if we could find one in common. If it’s one single plugin that’s one thing, if it’s different ones for each of us – then the fix would be directed at you.

    Plugin Author Dzynit

    (@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

    Plugin Author Dzynit

    (@dzynit)

    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

    Dzynit

    (@dzynit)

    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.

    Plugin Author Dzynit

    (@dzynit)

    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.

    Plugin Author Dzynit

    (@dzynit)

    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.

Viewing 15 replies - 61 through 75 (of 102 total)