Nathan Rice
Forum Replies Created
-
Forum: Plugins
In reply to: [Atomic Blocks - Gutenberg Blocks Collection] “Layouts” selector not ShowingOne extra note, Atomic Blocks is no longer where we are dedicating time to active development of our block library. Instead, active development is now happening in our replacement plugin, Genesis Blocks.
While we will be fixing bugs like this one in Atomic Blocks for a time (so people have time to switch to Genesis Blocks), eventually this plugin will be retired and no longer maintained.
We highly recommend switching to Genesis Blocks and running the migration tool, especially if you need this bug resolved quickly, since the latest version of Genesis Blocks doesn’t have this bug.
Forum: Plugins
In reply to: [Genesis Simple Sidebars] Header sidebar included in selectionI’ve added this as a feature request in the next version of Simple Sidebars.
Forum: Plugins
In reply to: [Simple Social Icons] Email icon uses HTTP instead of mailto protocolThere is code in the plugin that is meant to prevent this:
https://github.com/copyblogger/simple-social-icons/blob/develop/simple-social-icons.php#L375If it is not working for you, then the built in WordPress function
is_email()is not returning true for the email address you entered.Forum: Plugins
In reply to: [Genesis Simple Edits] Fatal error in 2.1.0This has been fixed, everyone. The latest version no longer uses a Genesis function in the boolean check.
Forum: Plugins
In reply to: [AgentPress Listings] WordPress 4.0 update changed listing search results@mymothersdaughter The plugin instructs WordPress to use the archive-listing.php template in the theme folder. Your problem is manifesting very differently than @pradeep11’s, which makes me think that your archive-listing.php file has been changed at some point, rather than WordPress using the search template, which was the original problem.
That’s what I would check. Make sure the archive-listing.php hasn’t been changed, or matches the file in the original AgentPress zip.
Forum: Plugins
In reply to: [AgentPress Listings] WordPress 4.0 update changed listing search resultsCan you both check to make sure you have version 1.2.2 installed and active on the sites in question?
Forum: Plugins
In reply to: [Genesis Simple Edits] Fatal error in 2.1.0Forum: Plugins
In reply to: [Genesis Simple Edits] Fatal error in 2.1.0The fix above actually changes the logic of that line to something other than what is intended. It goes from asking if the child theme supports HTML5 markup, to asking if Genesis 2.0+ is active.
So, I would not recommend that as a fix.
I’m curious about the manifestation of this bug. Are you network activating this plugin? If so, don’t … unless you can be sure that every site in the network will be running a Genesis child theme and you are running the latest version of Genesis.
This bug is effecting Genesis 2.0 sites running older themes that need xHTML theme support enabled.
It shouldn’t be. That line is what checks for HTML5/xHTML support. If a child theme is still running xHTML, that line will determine to use xHTML markup instead of HTML5. If you are getting the “undefined function” error, it means that either you’re not using a Genesis child theme, or you are running a version of Genesis older than 2.0.
Forum: Plugins
In reply to: [AgentPress Listings] WordPress 4.0 update changed listing search results@alex & @mymothersdaughter Sorry about that … I synced the SVN repo with the wrong Git branch and it had some old code that caused this error. I’ve pushed out 1.2.2 and it should work as intended now.
For those of you who are not getting the upgrade notification, there’s nothing we can really do about that. Best option is for you to just manually update the plugin using FTP if there is any urgency involved.
The plugin README says identifies the plugin as being tested up to 4.0.0, so everything is fine there too.
Forum: Plugins
In reply to: [Single Post Template] 1.4.4 Should fix issuesI can’t duplicate this. I have 1.4.4 installed on a test site, I’ve placed a template in my theme folder with the following at the top of the file, and I get the selector just fine when editing a post.
<?php /* Single Post Template: Special Post Template */One thing you might try is clicking the “Screen Options” slide down tab at the top right of the edit post screen. Make sure you check the box that says “Single Post Template”.
Forum: Fixing WordPress
In reply to: Main $wp_query returning WAY too many posts.Thanks to Mark Jaquith, this issue is resolved.
Turns out, because we use sticky posts to populate a slider, and I never thought to clear out posts from being sticky after they no longer need to be featured, we had 4000+ sticky posts. The main query was pulling all these guys in, causing the massive query mentioned above.
Cleared out the stickies (and wrote up a limiter so this doesn’t happen again) and we’re back to smooth queries.
Thanks so much to Mark for hunting this down!
Forum: Fixing WordPress
In reply to: Main $wp_query returning WAY too many posts.One thing I have done to circumvent this issue is to simply set a static homepage. If I’m gonna waste a query, at least this is a simple one to waste. (the homepage content is going to be custom queries anyway, so I really should have done this ages ago).
The bug still irritates me, but at least I’m getting decent performance now.
Forum: Fixing WordPress
In reply to: Main $wp_query returning WAY too many posts.Steve,
Unfortunately that’s over my head. I know very little about raw SQL interaction.Forum: Fixing WordPress
In reply to: Main $wp_query returning WAY too many posts.BTW, if I try to do a new query …
$q = new WP_Query( array( 'posts_per_page' => 10 ) );… and
count()those results, same thing happens. But as soon as I add a category or author parameter, it starts honoring theposts_per_pageparameter.Possibly unhelpful or unrelated, but strange nonetheless.
Forum: Fixing WordPress
In reply to: Main $wp_query returning WAY too many posts.Migrating via the WP export/import features is absolutely impossible. Too many posts, too many comments, and WAY to many image attachments to practically move over. When changing servers, we almost always have to move the files manually, and do a SQL dump to get it to the new server.