SN0WKRASH

Still broken – any fix?!

If we don’t get a fix in a few days we are dropping it because it doesn’t work. Thanks for a few months of working ??

We are having the same problem. Any fix for this?

https://www.ablogtowatch.com/about/

right column – big empty space.

Thank you for your attention.

The Plugin Organizer plugin does not allow selectively loading/not loading based on category. I’m hoping this plugin starts getting maintained so we can use it.

@esmi Wow, thought the fact I was having the same problem and giving more information to facilitate a fix would be helpful. Forgive me, seemed like setting up a new topic when it’s the same topic would be splintering and not make sense.

Sorry for this rudeness!

I’m having the same problem.

Suddenly, my admin area sidebars disappeared. After disabling each plugin I hit this one and the sidebars came back. The whole time, the sidebars were appearing on the site with their widgets, these widgets included, but in the admin area the sidebars in the Appearance -> Widgets area just were not there.

I’ve disabled it for now, but I am really hoping it gets fixed and an update is released soon. We miss the Instagram widgets we had set up.

Thanks.

Okay, I updated the plugin again with the one you released about 10 hours ago and I am no longer getting the error and it is working well otherwise. Thank you!

I’m seeing this error in my error logs when I try to index:
WordPress database error You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'LIMIT 400 /* From [www.ablogtowatch.com/wp-admin/options-general.php?page=releva' at line 17 for query SELECT post.ID\n\t\tFROM wp_posts post\n\t\tLEFT JOIN wp_posts parent ON (post.post_parent=parent.ID)\n\t\tLEFT JOIN wp_relevanssi r ON (post.ID=r.doc)\n\t\tWHERE\n\t\tr.doc is null\n\t\tAND(\n\t\t\t(post.post_status IN ('publish','draft','private','pending','future')\n\t\t\tOR\n\t\t\t(post.post_status='inherit'\n\t\t\t\tAND(\n\t\t\t\t\t(parent.ID is not null AND (parent.post_status IN ('publish','draft','private','pending','future')))\n\t\t\t\t\tOR (post.post_parent=0)\n\t\t\t\t)\n\t\t\t)\n\t\t)\n\t\t AND post.post_type IN ('post', 'page', 'ask_us_anything') LIMIT 400 /* From [www.ablogtowatch.com/wp-admin/options-general.php?page=relevanssi/relevanssi.php] in [/nas/wp/www/cluster-1816/ablogtowatch/wp-content/plugins/relevanssi/lib/indexing.php:103] */ made by require_once('wp-admin/admin.php'), do_action('settings_page_relevanssi/relevanssi'), call_user_func_array, relevanssi_options, relevanssi_build_index, referer: https://www.ablogtowatch.com/wp-admin/options-general.php?page=relevanssi/relevanssi.php

I’m having the same problem. I’m showing something on the “front page,” and the plugin offers no way to show on page 2,3,4, etc. of the front page. A fix happening for this???

Thank you.

Guess what? After hitting my head against a wall for almost a month I found the answer.

In “Advanced Options” on the settings screen, I unchecked “Revisions” in the “Supports” area. Why would supporting revisions completely disable saving or previewing the post????

I’m having the same problem – is this something that will be fixed in a plugin update?

Meanwhile, I’ll add the line of code eried suggests and see how that goes.

Thanks for responding quickly.

No, I do not know how to do anything with custom post types beyond what I have laid out here. It happens when I try to preview a post, as well – not trying to save it.

I am also seeing this error a lot in the error logs, and after some research, it turns out this happens when either the custom post type is getting registered incorrectly or when a post type that does not exist is being called or queried:

[Mon Feb 03 09:51:54 2014] [error] [client 157.55.34.29] PHP Warning: Illegal offset type in isset or empty in /nas/wp/www/cluster-1816/ablogtowatch/wp-includes/post.php on line 1060

I found something online that looks similar to this:

https://wordpress.stackexchange.com/questions/19000/illegal-offset-type-in-get-post-type-object?answertab=active#tab-top

It’s saying that a post type is being referred to that doesn’t exist, basically, so wondering how that could be happening.

Any ideas?

Thank you, Kristin

I’ve deactivated all plugins, even Jetpack, and I still cannot save or preview the custom post type.

Any ideas beyond a php error? There were no errors in my logs before or after deactivating plugins. Would re-naming the custom displays on the front-end cause problems on the backend like this? I’ve renamed according to what WordPress says to do and it works on the front-end but that’s when the back-end started not to save… think about it – when you go to preview a page, it looks for what the page name it thinks it should be exists, so if it can’t find it, wouldn’t it behave this way? If that’s it, then what should the pages be named if not what WordPress templating dictates?

Hello,

I’ve tried all the usual things, deactivating plugins, etc. I still have no Twitter meta data showing up in the source.

Help, please, suggestions welcome – this is affecting more than one of my clients.

Thank you,

https://www.ablogtowatch.com

I am unable to get two of my clients’ sites to show the metadata for Twitter using this plugin. Therefore, the validator will not validate.

Was your issue that you did not see the metadata in the source, or was the issue something else?

I would rather change the featured image size to what I want to use – I feel WordPress should provide that as an option in the media area as it does with the small medium and large images.

Apart from that, does anyone know where I would change this setting using my child theme off of twenty-fourteen? It’s gotta be a function I can put in the child theme functions file.