joycegrace
Forum Replies Created
-
We have the same issue on multisite.
Will there be a release to fix this soon?
(Just so you know, another thing that happens is that the private posts start not appearing on the front end of our site. Disabling this plugin brings them back. Yes we deactivated all plugins on our site and reactivated one by one. This is the culprit.)
@tunjic – did you notice that activating it on ID=1 blog fixed it network wide as well, or only on that one blog?
@mchildress – can you walk us through the permissions we should look at to fix this?
Thanks all!
Forum: Plugins
In reply to: [Slideshow Gallery LITE] wp_head and wp_footer errors showing after upgradeWe are having this problem while using the Genesis Framework. We can’t figure out why the error is there. We don’t have a caching plugin or maintenance mode plugin – the site is live.
Is this error showing because Genesis doesn’t use the typical footer.php and header.php in the child theme folder?
How can we work around this? Can you please provide a solution?
Forum: Plugins
In reply to: [WooCommerce] Remove "categories" and "tags" words on product pages?Hi Lorro!
First of all, thank you so much for your help on this.
We found it wasn’t working as well as we wanted it to, but we did come up with this, which is working for us:
span.sku_wrapper {visibility:hidden}
span.sku_wrapper span.sku {visibility:visible}
span.sku_wrapper span.sku::before{content:”SKU: “}span.posted_in {visibility:hidden}
span.posted_in a {visibility:visible;}
span.posted_in a:first-child {display:inline-block;margin-left:-25%;}
span.posted_in a:last-child::after {content:””}
span.posted_in a::after {content:”,”}span.tagged_as {visibility:hidden}
span.tagged_as a {visibility:visible; }
span.tagged_as a:first-child {display:inline-block;margin-left:-10%;}
span.tagged_as a:last-child::after {content:””}
span.tagged_as a::after {content:”,”}I hope it helps others who are looking!
Forum: Plugins
In reply to: [WooCommerce] Remove "categories" and "tags" words on product pages?Wow thanks for your help! It did work, sort of, but it also got rid of the commas between the actual taxonomies: http://cl.ly/image/281F253z0L1g – do you happen to know how we can bring that back?
I understand if it’s too challenging, like the period 🙂
Thanks so much!
Forum: Plugins
In reply to: [Fast Secure Contact Form] How to delete forms?Will this be added eventually? The ability to at least delete the fields we don’t want to use instead of having to disable them? I know this is a bit of another subject, but it really would be ideal.
Forum: Plugins
In reply to: [Fast Secure Contact Form] How to delete forms?I see under “Tools” there is an option to delete a form sometimes, but not always? It says “Form 1 cannot be deleted” – I guess this is just the first form that must be started with?
Forum: Plugins
In reply to: [Manual Related Posts] Documentation ?Yes I would also like to know the answer to this
It appears the update to WordPress SEO resolves the Syntax error now, with or without switching to Php 5.3
You need to apply for a twitter card, but I don’t think it’s working right now, see this thread http://wordpress.org/support/topic/invalid-markup-twitter-card-metas-solution?replies=3
Hello, is this why when I apply for a Twitter meta card it now says it is an “invalid card type”? See screenshot: http://d.pr/i/gKLU
Did Twitter change their application process? I am using the Yoast plugin to set this up and when I apply for a card, it wants me to pick a card type. So I select “summary” (because I read that the plugin pulls “summary” as a default) and then when I enter the URL, it says it is an invalid card type. I tried it with other card types as well. Do you know if this is a problem with the Yoast plugin or something I could be doing to change this somewhere? Can you tell me what files to change and where? Thanks!
Adding a robots.txt file to your web directory will over write the default one that WordPress uses.
Note that you can be no-indexing things with the WordPress SEO plugin that aren’t included in your robots.txt file
I would give Webmaster Tools time to learn about your new settings.
You are probably no-indexing some pages or category archives in the WordPress SEO settings, and then including them in the sitemap, when they should not be included. If that doesn’t solve it, I would go to the sitemap settings for where the excluded robots.txt exclusions are and force it “never include.” Or you can set the index to “always index” and include in sitemap. The two should work together – if something is in the sitemap, it should not be blocked by the robots.txt file. Also of note is that you can have a manual robots.txt file and also have other pages no-indexed by the WordPress SEO plugin that won’t show in the robots.txt file on your server.
I have added Canadian English language files and also changed the wp_lang in the wp-config file to en_CA and it still shows as en_US
Laffaireboudet, or anyone out there, if you know a way to fix this, can you let us know?
Thanks for the reply. It is when I click on that button to clear the error message that I am told I don’t have sufficient permissions to view that page. 🙁
I am getting this error when I try to delete the error messages after having resolved the issue.
I am an administrator, and this is a single installation of WordPress. The whole back end of the WordPress site shows a red error box that a tweet was not sent. I just re-did the keys with twitter and it says it’s connected now, but the error message won’t go away.
It says “There’s been an error posting your Twitter status! Visit your WP to Twitter settings page to get more information and to clear this error message.”
And on the settings page of this plugin there is one that says:
“One or more of your last posts has failed to send a status update to Twitter. The Tweet has been saved, and you can re-Tweet it at your leisure.
401 Unauthorized: Authentication credentials were missing or incorrect.”
I really need these to go away, can you help? I might have to use another plugin otherwise since red error boxes can be scary to a client.
Thanks for your help