kalligator

Thankfully I unearthed the old group url, the one it used to have before I gave it a slug and it works!

https://www.facebook.com/groups/123456789012345/

/edit/
I wasn’t getting any errors, SNAP was simply posting to the FB profile page instead of the FB group.
That’s when I was using the current group url, like so:

• http//www.facebook.com/groups/word1.word2/

Once I entered the old style url:

• https://www.facebook.com/groups/123456789012345/

it worked properly and posted in the group.

In case it’s of any relevance, the profile and the group url are almost identical.

https://www.facebook.com/word1.word2/
https://www.facebook.com/groups/word1.word2/

I updated my previous post – no workie!

I hadn’t noticed your reply, I’ll try that next time, thanks.

you need to manually download the 0.52 version, extract it’s contents and then using an ftp client upload these files to the appropriate folder (wp-content\plugins\widget-logic), overwriting the existing ones.

Oops I hadn’t noticed, sorry

WP 3.5, WL 0.54:
Parse error: syntax error, unexpected T_ENCAPSED_AND_WHITESPACE, expecting T_STRING in /home/XYZ/public_html/wp-content/plugins/widget-logic/widget_logic.php(284) : eval()'d code on line 1

Thanks, I’ve done that in the meantime, it’s not hard at all.

However in the future I’ll try and abstract this from direct theme hardcoding into the plugin options so as to make it easy for the user to choose.

Can you give me any hints on which files should I focus?

Turns out I had the wrong idea for the categories filter to begin with. It only applies for ad injection.

Does anyone have any idea on how to build such a feature, where normal shortcode ads are aware of the categories / tags we set them for and show or hide accordingly?

Please ignore my previous comment, it’s not a WP 3.5 specific error, I got the problem on a WP 3.4 installation as well.

My host migrated the server recently and apparently something is not quite right there. I now get memory exhaustion (64M) errors all over, it doesn’t seem to adhere to the wp-config & php.ini overrides of 256M I’ve had in place anymore.

Both installations had wp-minify working fine before.

And to answer your question, the error I get from minify is PHP Warning: filemtime() [<a href='function.filemtime'>function.filemtime</a>]: stat failed for /home/XYZ/public_html/wp-content/plugins/wp-minify/cache/9fc5294425effd4de4a7223f9931cef5.css in /home/XYZ/public_html/wp-content/plugins/wp-minify/wp-minify.php on line 625

On WP 3.5 it’s giving me 404 for the css

@gfazioli any news on the real time rotation? wpxtre.me does not mention it.

I’m interested in that as well.

To make them go away completely you need to apply stripslashes() to all instances of get_option($widgetID.'-conditional-tags'); in the ajax.php and custom.php files, so they become: stripslashes(get_option($widgetID.'-conditional-tags'));

@david revert your file to the original and then apply the above replacements.

I’m interested in using the shortcode, not hardcored.

It’s not that I find it hard to remove it myself from the library but clients may find the process somewhat painstaking.