nashvillegeek
Forum Replies Created
-
Yeah, Eddie Machado’s Bones theme removed the add_action sometime back. The site in question was built prior to the update. I appreciate your timely responses.
The issue for us is ‘add_theme_support(‘post-thumbnails’);’ was called after theme setup. We changed the code as follows:
// add_action(‘after_setup_theme’,’bones_theme_support’);
bones_theme_support();Featured images are functioning as expected.
I’ve isolated this down to a theme issue. Strange that it is only associated with AIOSEO activation. I’ll post back if I figure it out. Thanks.
I have the same issue. I disabled all plugins. When AIOSEO is activated, console shows the error:
event.returnValue is deprecated. Please use the standard event.preventDefault() instead. XHR finished loading: "http://website.com/wp-admin/admin-ajax.php". load-scripts.php?c=1&load%5B%5D=jquery-core,jquery-migrate,utils,jquery-ui-core,thickbox,underscore…:5 send load-scripts.php?c=1&load%5B%5D=jquery-core,jquery-migrate,utils,jquery-ui-core,thickbox,underscore…:5 x.extend.ajax load-scripts.php?c=1&load%5B%5D=jquery-core,jquery-migrate,utils,jquery-ui-core,thickbox,underscore…:5 e load-scripts.php?c=1&load%5B%5D=hoverIntent,common,admin-bar,schedule,wp-ajax-response,autosave,jqu…:74 (anonymous function) load-scripts.php?c=1&load%5B%5D=hoverIntent,common,admin-bar,schedule,wp-ajax-response,autosave,jqu…:74This message continues to generate. De-activate and everything works as expected.
That’s it! Everything is working now. Thanks @bredon!
I installed the newest version of bones. The featured image functionality is as expected when AIOSEO is activated. Perhaps something in previous versions of bones, or maybe a custom post type is causing the issue. I’ve used these together on other sites with no issue. I’ll post if I figure it out.
Not in the screen options at all for regular post types or custom. Deactivate, and everything is there. The strange thing is all of the other options are still there when activated.
I switched to twenty twelve theme, and it looks like there must be something in my theme conflicting with AIOSEO. I have no idea what it might be.
Thanks for your response. I’ll post if I figure it out.
I’m just as confused. The featured image metabox disappears across all post types and pages, and the option doesn’t show up in the screen options. I’ve deactivated all plugins and tried each one at a time. I even removed my custom post types, extra JS files, etc to see if something there was causing it.
The theme is based on the Bones theme, and I use several plugins like Advanced Custom Fields, Post 2 Post, AIOSEO and Advanced Recent Post Widget. I can’t rule out something in my code, but AIOSEO is the only plugin that affects it directly with activation/deactivation.
Strange stuff. Just thought I’d check to see if you’ve had this before.
Thanks
That worked seamlessly. We could do this because we hadn’t input any SEO descriptions yet.
$wpdb->query(“UPDATE $wpdb->postmeta SET meta_key = ‘description’ WHERE meta_key = ‘_aioseop_description'”);
then, to preserve custom field entries in the future, renamed custom field ‘description’ to something else:
$wpdb->query(“UPDATE $wpdb->postmeta SET meta_key = ‘your_own_prefix_description’ WHERE meta_key = ‘description'”);
I actually did the updates in phpMyAdmin so the query was:
UPDATE
postmetaSET meta_key = ‘description’ WHERE meta_key = ‘_aioseop_description’Thanks again!
Thank you. I can just reverse those meta keys to revert, and then rename the custom field meta to something more cryptic before using All In One SEO.
Thank you for your help.
Lesson learned. Can you tell me where I can find the description field those entries were moved to in the database? i.e. the AIOSEO description field
thanks
Thank you for your response, Peter. Apparently, the button was pressed, which moved those fields from our custom post type description fields to the AIOSEO description field, which was not a desirable outcome. The database was backed up prior to the pressing of the button and work forged ahead for a few days. Now we see the button again, and many description fields in AIOSEO instead of their original place. If pressed, are you saying that the new entries will be moved into AIOSEO, as well? I need to prevent this from happening on other sites in the network.
Do you have any suggestions on how to revert the moved entries back to their appropriate custom field without losing the entries which were entered after the button press? Perhaps a script that has the opposite affect. It seems I will need to rename our custom field name to avoid conflict with this feature of your plugin. Not sure of the impact that will have on previous entries.
I appreciate any guidance.
Forum: Plugins
In reply to: [Firelight Lightbox] Bones Theme IssueDefinitely. Thank you!
Forum: Plugins
In reply to: [Firelight Lightbox] Bones Theme IssueGot it. The example on your site was missing the fancybox-inline class. The settings area clarified. Adjusted code is below.
Read my inline content
<div style=”display:none;” class=”fancybox-hidden”><div id=”fancyboxID-1″ style=”width:460px;height:380px;”>
…inline content here…
</div></div>Forum: Plugins
In reply to: [Firelight Lightbox] Bones Theme IssueWell, images work but inline content won’t load. It says, ‘The requested content cannot be loaded.’