|
Simon van Gool
|
February 20, 2013 at 9:07 pm
WordPress Version: 3.5.1 PHP Version: 5.2.17 MySQL Version: 5.0.95 Event Espresso Version: 3.1.30.7P WordPress Address (URL): http://www.atfa.com.au/wordpress WordPress Content Directory: /var/www/vhosts/atfa.com.au/httpdocs/wordpress/wp-content Site address (URL): http://www.atfa.com.au/wordpress Event Espresso Plugin URL: http://www.atfa.com.au/wordpress/wp-content/plugins/event-espresso/ Event Espresso Plugin Path: /var/www/vhosts/atfa.com.au/httpdocs/wordpress/wp-content/plugins/event-espresso/ Event Espresso Upload URL: http://www.atfa.com.au/wordpress/wp-content/uploads/espresso/ Event Espresso Upload Path: /var/www/vhosts/atfa.com.au/httpdocs/wordpress/wp-content/uploads/espresso/ Event Espresso Template Path: /var/www/vhosts/atfa.com.au/httpdocs/wordpress/wp-content/uploads/espresso/templates/ Event Espresso Gateway Path: /var/www/vhosts/atfa.com.au/httpdocs/wordpress/wp-content/uploads/espresso/gateways/ I have a brand new install of Event Espresso and it seems to be working fine until the Ticketing plugin is activated. It seem to over ride my theme CSS and breaks all the fonts and colour settings. Any Ideas? I have looked to see if there is a setting in the Events admin to control CSS, but I can’t see anything relating to ticketing.
-
This topic was modified 11 years, 2 months ago by
 Simon van Gool.
-
This topic was modified 11 years, 2 months ago by
 Josh.
-
This topic was modified 11 years, 2 months ago by Josh.
|
|
Dean
|
February 21, 2013 at 1:27 am
Hey Simon,
There should be no reason why the ticketing add on should affect the front end CSS.
Is it affecting the full site or just Event Espresso related pages? Is there an example somewhere I can see?
|
|
Simon van Gool
|
February 21, 2013 at 3:56 am
It effects every page, including site navigation menu, body content and h1/ h2 / h3 tags etc. Screen Shots here
http://webcrowd.com.au/deactive.png
http://webcrowd.com.au/active.png
The only difference between those shots is deactive has the ticketing addon turned off, and active has it turned on. As you will see when I turn it on (active) all the fonts default to times and some of the colours goto black. Not shown in the screen shot, but it also messes with the hover colours on the navigation menu.
|
|
Dean
|
February 21, 2013 at 4:17 am
Hi,
Is it possible to get your login details in order to look into this? I actively would like to turn the add on, on and off to see if there are jquery issues, css issues etc.
If so, please send them via https://eventespresso.com/send-login-details/
NOTE: login details need to be Admin level.
|
|
Dean
|
February 21, 2013 at 6:01 am
Hi Simon,
I have never seen this before. There are no jquery errors but when the add on is enabled two php files from the theme suddenly hit a 500 internal server error, and one of these controls some of the css, resulting in the issue.
I think there is a conflict between theme and plugin here, but as to what that conflict is i am not sure, I am going to have to do some more testing on it.
Ok so I did some more testing locally, and I will have to refer this to a developer to see if we can pinpoint the issue more, there is something occurring where the style.php file on my local server is throwing out an error to do with wp-includes/rewrite.php a core WP file.
Regarding the no content in the editor issue you mentioned in your email, that is theme and event espresso related. Theme due to them modifying the editor and event espresso due to the way we request the editor. We have rebuilt the admin system in 3.2 so this should stop or reduce conflicts like this.
Currently the only resolution is to avoid systems like Lambda which heavily modify the interface.
|
|
Simon van Gool
|
February 21, 2013 at 6:13 am
Thanks Dean
When is 3.2 due for release?
I look forward to hearing about the CSS issue.
Simon
|
|
Josh
|
February 21, 2013 at 10:57 am
Hi Simon,
It looks like your custom styles are being loaded from the theme’s options via PHP. I’d suggest trying to add them to your child theme’s style.css to see if that makes a difference. I don’t know why the ticketing add-on would affect the dynamically loaded styles, but this may fix the issue for you.
|
