takoateli

Thanks for your help. It seems that if any of the event fields are empty then Google won’t crawl them.

Thanks for the reply! Has something changed with the plugin which would have fixed these issues?

I have submitted new xml sitemaps so I think that will trigger a crawl.

Thank you very much!

Thanks! I would like to show the descriptions please even if it’s less than ideal.

Yes. Thanks. Today I learned the difference between deleting a plugin and deleting it’s folder.

Folks here’s an update. Setting the plugin to safe mode didn’t stop the crashing. Here’s what I needed to do, install the plugin, WITHOUT ACTIVATING IT DELETE IT, then reinstall and reactivate it. What gave me the clue was the uninstall.php file. I looked and saw there was a lot of cleanup on the way out.

So if you add a snippet and crash the site and need to delete the plugin folder to get it going, follow the steps above and you’ll be back in business.

Thanks! Yes, I’m trying to find the source of that error. I was just troubleshooting with the host (WPEngine). Disabling plugins doesn’t eliminate it. Switching themes does. I’m trying to dig into that and see what’s going on.

Thank you for your reply sterndata. My understanding is the player is embedded hidden, and then when the page is rendered and the footer is called then the player is initialized and displayed. So it’s normal that as the page is loaded (but before it’s finished loading) that the player would be hidden, but it shouldn’t be that way when the page is done loading.

Thanks for the reply.

I understand the free/paid plug-in model. The free mode lets you test compatibility and functionality, and the paid mode enables extended features. Typically the author hopes the free users will convert to paid users.

I like your plug-ins, you guys do a good job. My only complaint is your business model. There is an attempt to steer users into a pricey subscription plan. Even when you purchase the plug-in out right you only get one year of updates, and it’s good for only ONE domain. Most other plug-in authors that are selling in your price range offer unlimited domains. I understand you offer discounts when one purchases more copies of the same plug-in for other domains, but the amount of the discount isn’t much. 10% for the second domain, 20% for the third domain, etc. And this is an annually recurring cost.

In some markets a vendor will make more money by dropping their prices because it will greatly increase sales. That may be the case here because if I find the plug-in in this price range that offered either unlimited domains or lifetime updates I would choose that over your product.

See the title of my post. Note the words “custom pagelines”

thank you so much! That worked perfectly!

Thank you so much! What I tried and what you’re seeing is CSS to remove the space after a paragraph. but of course that is site wide and has effects on other areas which I would rather didn’t occur. Is there only way to remove the spaces after paragraphs only on the home page, or just for widgets?

Thanks! I did search the forum first.

You pointed me right to what I needed. Thanks!

It’s generous helpful users like you that make the forums so great.

Krishna, I understand what you’re saying about the troubleshooting steps you suggested. Those are basic WordPress troubleshooting 101 procedure. The steps you pointed out are what one would do to troubleshoot using a single site. It is the most direct way to troubleshoot. it’s the most direct way to troubleshoot, but it is also extremely disruptive to the site. That’s fine for somebody who’s just running a blog, but for someone with a production site that can’t be shut down it is not applicable. However, even without being able to perform the steps above there is a way that we can troubleshoot on a grander scale. Since there are many people who frequent this forum who use the same theme, plugins, and CDN network (CloudFlare), we can do a distributed form of troubleshooting. If there is some incompatibility between these commonly used components those incompatibilities will present themselves too many users.this trouble shooting technique is extremely useful when dealing with an intermittent problem. Troubleshooting an intermittent problem on a single installation can be misleading. Troubleshooting an intermittent problem across many users is usually much more revealing.if many people have the same symptom and the only thing they share in common is one plug in then the results are conclusive even though the issue is intermittent. That goes to show an example of when the kind of troubleshooting I’m hoping we can do in this case is actually the ideal. In my presence situation I would rather do the troubleshooting that you suggested, but because it’s a production machine I’m hoping that this post might draw comments from other people who were having the same symptoms and we can find what we share in common and hopefully determine the cause.

I really can’t. That’s a production site and I can’t be doing that. I know that I have had this issue with both the Super Cache plugin and also the W3 Total Cache plugin. I’ve also had the issue across more than one version of WordPress. I’m having it with this version and I had it with the version previous. I really think this issue does have something to do with CloudFlare because that’s the only thing that’s new in the mix.

Greg