How often are the theme mods changed? A lot in the design phase, maybe a couple of times later on. Always by admins, never by ordinary users, let alone visitors. So, it doesn’t make sense to generate the full css at every pageload (additional background info). A better approach is to generate the css only … Read more
I prefer separete all my front-end assets from the back-end, so I use Gulp to manage (compile, mifify etc..) all my assets. But if you want to use WordPress I found this article. I did not test the code, but by just reading and seeing the comment section I think that will work for you. … Read more
My recommendation would be to set up a wrapper for fetch_feed(). Call the wrapper function through WordPress’ cron and you shouldn’t have an issue. So something like: function schedule_fetch_feeds() { if ( ! wp_next_scheduled( ‘cron_fetch’ ) ) { wp_schedule_event( time(), ‘hourly’, ‘cron_fetch’, ‘http://blog1.url/feed’ ); wp_schedule_event( time(), ‘hourly’, ‘cron_fetch’, ‘http://blog2.url/feed’ ); } } function fetch_feed_on_cron( $url … Read more
Answer: as of 3.3 and beyond, a “problem” structure now only adds one single optimized query. I wrote a post about that, in fact. Bottom line: it’s no longer an issue. You’re welcome. 😉
WordPress should behave the same, only dependent on your server resources. I hope you have a dedicated server because if not then you will experience severe outages and possibly cancellation of your hosting service. WordPress is merely databases and PHP, so amount of files will not affect its use. It is stable. You could have … Read more
I know this is really old question, but today I was dealing with something similar, and I have found a solution – if wp_unique_post_slug() calling is performance bottleneck, and post_name value is not important, then set post_name manualy to some random value. My wp_insert_post post action was taking too long lately (20-30s). It saves custom … Read more
You can use “W3 Total Cache” which isn’t a static file cache system. It however uses stuff such as opcode caching, memcached, and object caching to decrease page load time. APC, or another opcache, would be a good addition to your server, as well as using a lightweight httpd instead of bloated Apache. Forcing GZIP … Read more
Create a local repository in Git (or SVN) for the plugin, and each time an update happens: merge the changes into your adjusted version, test it in your local copy of the production site, then push your updated code to your site. But much better would it be to send your improvements to the plugin … Read more
Removing the hierarchical parameter from the register_post_type function call did the trick, as per vancoder’s suggestion. On the back end, looking at what the hierarchical option does (set the new post type to behave like the page post type) tells me that it probably shouldn’t have been set in the first place.
If it’s exactly the same code, then no – it shouldn’t cause any performance changes… Why? Because loading a plugin is pretty easy (hence quick) process. It all happens in wp-settings.php and this is the code: // Load active plugins. foreach ( wp_get_active_and_valid_plugins() as $plugin ) { wp_register_plugin_realpath( $plugin ); include_once( $plugin ); } unset( … Read more