Forum Replies Created
-
Posts
-
Howdy Rafael,
IE & FF both have a default style if you view the feed directly like you are doing. The default stylesheet hides everything except the title, content snippet, and publish date. Chrome on the other just displays the raw data. If you right click in FF or IE and click view source you will see the raw data, same as Chrome. So really the data is there, IE & FF are just hiding it with their default stylesheet.
In my opinion Chrome’s lack of styling makes the most sense, considering over 99% of the views an RSS feed gets are from feed aggregators (computer algorithms) who are programmed to only care about the raw data.
I have never tried to override IE & FF’s default styles. It might be possible using a stylesheet. However you will notice that nearly everyone recommends you not bother with styling RSS feeds. For one thing not all browsers support it. For another you, the person styling it, are probably one the only people that will ever see it style since feed aggregators will completely ignore this. But, if you want to mess with styling it might be possible using a stylesheet.
Does that make sense? If you do go ahead with styling I’d be interested to see how it turns out.
– Brook
Howdy Finleydesign,
You would generally use paddings and margins to correct cropping issues like that. I am actually not seeing the issue on my browser, but since everyone’s browser is different that is not surprising.
There are some problems with the current CSS layout techniques, and you are going to face quite a few issues as time goes. One example is if you adjust the size of your browser window so that it is small, or simply view this on a mobile phone, you will see overlapping content everywhere. Your footer navigation is not appearing in the right place on my screen, and it will not on many peoples. Furthermore, on other venue pages as content grows or shrinks things will be positioned wrong, and might even overlap. To truly fix all this you would need to rewrite the modifications from scratch using different techniques. If you are not experienced enough in CSS to do that, you might consider hiring someone who is.
Best of luck! I hope the rest of the site goes smooth.
– Brook
Howdy Heidi,
You did awesome so far, it look like you have the right setup going. I just put an override in the same place and the change is showing up. I can think of a few things that might be hiding your changes from you though:
– There are some if/else blocks within that file. Perhaps your changes are within one of those, and not showing up because the conditions are not met.
– If there are no posts for a venue this file will not really show much. Perhaps there are no posts for that venue?
– Maybe the changes are going through but are being hidden by some CSS. Have you double checked the source of the page?Please let me know if one of those helps. I sure hope so, or else this would be quite puzzling. Thanks for posting!
– Brook
Howdy reshetramah,
Is the entire front-end of your site showing a white page, or just one of the page? Is the backend showing white as well?
If you can access the backend WP-Admin area, can you try going to Settings > Permalinks and clicking save?
Thanks for testing one-by-one. Narrowing it down like that is a huge help.
– Brook
Howdy Pat,
I wish I had some better news. Right now the only user who has fixed it was the one who rolled back, which is what I would recommend in your case. Our 3.4 update which also fixes this is due out very shortly, but unfortunately that is as specific as I can get in terms of a release date. If your client can wait a week and see if an update has materialized, if I were you I’d encourage them to take that risk. If not, a downgrade is in order.
I am very sorry for the inconvenience and unknowns. They are am inevitable part of software development, but I still wish I could do more. Let me know if you have any questions. Thanks!
– Brook
Howdy again Rafael,
First of all, sorry for the delayed response. I was not notified of your reply. It was only when one of our moderators did a pass of the forum did we notice that this topic needs a reply.
IE & Firefox do bring out a good point. Notice on line 9 of your feed that there is not a line break between the two xmlns. To fix this we will need to add a line break to our events_rss2_namespace() function like so.
Does swapping that snippet out for the one function currently in your functions.php file fix it for? You still need to keep the tribe_rss_feed_add_eventdate() function and associated actions. Please let me know. Thanks Rafael!
– Brook
Howdy runekjensen,
The heading color is specified within tribe-events-theme.min.css. Since it is a minified file a line number would be useless. To override the heading color I would use the following code to make it black:
body #tribe-events-content .tribe-events-tooltip h4{ color:#000; }The event background color is specified in tribe-events-pro-theme.css on line 30. I’d use the following rule to override:
body .tribe-grid-allday .hentry.vevent > div,
body .tribe-grid-body div[id*="tribe-events-event-"] .hentry.vevent,
body .tribe-grid-allday .hentry.vevent > div:hover,
body .tribe-grid-body div[id*="tribe-events-event-"] .hentry.vevent:hover {
background-color: #000;
background-color: rgba(0, 0, 0, .75);
border-color: #333;
}Does that help? Please let us know. Thanks!
– Brook
Howdy Jerry!
1) Yes, this is a builtin functionality of WooCommerce itself. You would go into WooCommerce and click “Add Order”.
2) If you have the correct PayPal account type. All WooTickets does is add WooCommerce products, and those products are your tickets. Thus, after the ticket/product is added to a users shopping cart WooCommerce handles it from there. You would want to consult with them if you have any questions about payment gateways like PayPal.
3) You can embed a buy it now button easily enough, and from there you can copy/paste any other info you want to appear on the page. Here is an example Add to Cart link:
<a href="./?add-to-cart=TICKETID" rel="nofollow" data-product_id="TICKETID" class="post-207 product type-product status-publish hentry first instock">Add to cart</a>You made it perfectly clear. Please let me know if you have anymore questions. I might not be able to help much if your questions are about WooCommerce functionality, which is supported by a third party. But, I will do my best. Any WooTickets questions I can definitely assist you with. Thanks!
– Brook
For sure. After diving into this a bit further it actually has nothing to do with HTML5 elements. In reality we do not support Ajax at all in IE9 and below, mostly because of those browsers lack of support for the History API. In a large part this is because of IE9’s steady decline (it has lost half of its users in the past three months alone), and that major websites like Google & YouTube do not support it at all. While we certainly did not go the YouTube route, we have found the lack of Ajax support to be a reasonable compromise.
– Brook
Howdy Keidrych,
Thanks for running through those troubleshooting steps and creating a new topic. I am as puzzled as you are. We never see 404 errors in the default setup. I have a few idea on things we can try.
This post outlines a few steps on how to fix 404 errors, mind running through them? If that does not fix it, you might try disabling then reenabling all of our plugins. Again, if that did not fix it, please try going to Settings > Permalinks and clicking save again. If that does not help, would you mind pasting this snippet into your theme’s functions.php, and adding a test event during the next month? That snippet will add a little bit of debugging info your theme’s source view for me to look at. If you get to this step and nothing has fixed it, please let me know once this snippet is in place and I will take a look at it. Thanks!
Let me know if you have any questions.
– Brook
Oh that makes sense! You are welcome Erin. Glad you got it fixed, and I appreciate your keeping us posted.
– Brook
If you were to click the “Find Events” button to the right, I think you will see it work as expected. I have to do that in my IE9 as well. I realize this is an extra click over some browsers. But, that is part of the reason why we made that button so giant.
IE9 lacks builtin support for much of HTML5 forms, and the datepicker element is new to HTML5. While I can not say with 100% certainty why IE9 is not autosubmitting, if I had to guess it has to do with IE9’s partial support of the standard. In instances like that we, like most developers, will support the browser but of course it will not get to take full advantage of new features.
Does that make sense? Were you able to get it working once you clicked the submit button?
– Brook
