Well, some event specific styles are added by default by eventpress—for the rest, it picks up files from the theme folder. However, there are bugs in handling child themes at the moment.
I was able to successfully customize certain areas by getting events.dev.css through FTP, editing it and then uploading it. I don’t know if that addresses your issue.
It’s at: /wordpress/wp-content/plugins/eventpress/themes/bp/assets/css/events.dev.css
It would be nice to be able to override the styles as-in a child theme – which is the first thing I tried. Why they chose to display events in an orange (#FFA200) instead of a neutral color is beyond me! Is that color likely to go with the majority of themes? I can’t show the site to the people in my group until I change it – it looks horrible! I hope I don’t have to fix it every time I update Event Press.
PS: and why is there a ‘dev’ in the name of that style sheet. To me that implies “development” as in “not finished”. I feel like I’m missing something.
The .dev.css is there because I’d started automating minimizing the .css and .js files using Phing/YUICompressor. While my code (switching between .dev.css and .css and .dev.js and .js was working by the time I pushed the current version of EP, I wasn’t completely sure that I had missed a file or two—hence the current version has *.dev.* includes.
The next version will ship with both, with the .dev.* files being included if SCRIPT_DEBUG and STYLE_DEBUG are set to true (basically mimicking how wp does it). And the orange colour was based on bp-default; ep’s styles were more or less completely written for the default themes.
I updated Eventpress on several of my sites and it keeps telling me I need to update:
“You have version 0.1.2.7 installed. Update to 0.1.2.8.”
Sure enough I look in eventpress.php and it says version 0.1.2.7
So either the WordPress update process is not properly updating (across 3 servers with different hosting companies) or it IS updating but the updated version is incorrectly saying it is 1.2.7.
Just curious as this is no big deal.
I am seeing the same thing as Kchun. Should we ignore this or not? Thanks.
I’m not sure why this is happening—the trunk source code that is committed has ep correctly set: http://plugins.svn.wordpress.org/eventpress/trunk/eventpress.php. The compressed file being created seems to be picking up previous versions.
