Forum Replies Created
-
Posts
-
Oh and mind you; that’s it’s not about the plugin not working with Genesis. I get that if it were a single theme it would be impossible to cater to every need. Genesis is a framework however. Utilizing WordPress core functionality. Like you should, which everyone should for that matter.
I’ve yet to see any plugin that adheres to those standards to clash with the Genesis framework or any well built theme.Come on!
You’ve got to be kidding us. You’re still creating content in WordPress like what used to be done in earlier years of WP. We have filters and hooks nowadays.Please take a look at:
http://codex.wordpress.org/Plugin_API/Filter_Reference/the_content
http://codex.wordpress.org/Template_HierarchyPlease use built-in WordPress functionality and there won’t be any plugin, theme nor theme framework complaining.
Thank you for your reply; my problem is not solved yet however.
I suggest focussing on Surbma’s thread:His issues are my issues.
Thank you for your comment Surbma, that’s what I was trying to communicate all along.
Especially about the “Default page template”. I didn’t even get to testing the archive pages yet..I’m keeping a really close eye on the reactions to this thread.
Thank you for your reply.
I get that turning WP_DEBUG doesn’t show you the errors, or notices in this case.
It’s also clear Strict doesn’t necessarily mean things are non-functional or incompatible, WordPress 3.6 however enforces Strict, meaning I should code around in core WP to turn it off?
As far as I know that’s not the Core – Plugin relationship works.I always have WP_DEBUG off on production, but it sure is still as annoying on development.
Obviously I have WP_DEBUG turned on my development; having the warnings appear breaks stylings etc. and makes it harder to find actual errors that pop-up when I am developing my own stuff. I actually use a little snippet like this (might be useful to others) in my wp-config.php:if( stristr($_SERVER[‘SERVER_NAME’], “twentwatchers.local” ) ) {
define(‘DB_NAME’, ”);
define(‘DB_USER’, ”);
define(‘DB_PASSWORD’, ”);
define(‘DB_HOST’, ‘localhost’);
define(‘DB_CHARSET’, ‘utf8’);
define(‘DB_COLLATE’, ”);
define( ‘WP_DEBUG’, true );
} else {
define(‘DB_NAME’, ”);
define(‘DB_USER’, ”);
define(‘DB_PASSWORD’, ”);
define(‘DB_HOST’, ‘live_db_host’);
define(‘DB_CHARSET’, ‘utf8’);
define(‘DB_COLLATE’, ”);
define(‘WP_DEBUG’, false);
}Seems WP3.6 enforces strict.
The events calendar (& PRO) update said it was compatible with 3.6.
Seems like this is not the case.. Unless you set WP_DEBUG to false.. then you won’t notice a thing. Was it off during dev?I’m in full agreement with Surbma here.
The thing is; once we get the REAL default template for Genesis, and we’re just able to add the event-details etc. via genesis-hooks it’s all sorted. We’d have the H1, (which it should be by default!) and all the other things are out of our way.
My thread with the same underlying issue:
https://tri.be/support/forums/topic/events-calendar-and-genesis-template-chaos/Really; a simple page template without any event calendar elements would be fine, as long as the data is available I’m willing to use the genesis hooks to add the information my self.
For now I’m just overwriting the styles in my theme’s CSS;
To give those rules more weight (ensuring overwriting) just place something like #content before the selector. (If the thing to be styled is in the content div, which it is most of the time ;))
