tanmccuin

Bumping this one and agreeing – i’m pretty much all in with Stackable but the lack of editable defaults is a glaring omission from an otherwise great tool. There so much free real-estate just waiting in the Stackable Global Settings tab ??

note for anyone looking for a fix in the meantime – you can comment out everything in the panoramic theme’s functions.php file from line 181 through 238 (essentially all the functions related to the theme registration notification message, which appears to be whats causing the critical error)

More details for theme devs

Fatal error: Uncaught Error: Cannot use object of type stdClass as array in .../wp-content/themes/panoramic/functions.php:204 Stack trace: #0 .../wp-includes/class-wp-hook.php(292): panoramic_admin_notice('') #1 .../wp-includes/class-wp-hook.php(316): WP_Hook->apply_filters(NULL, Array) #2 .../wp-includes/plugin.php(484): WP_Hook->do_action(Array) #3 .../wp-admin/admin-header.php(288): do_action('admin_notices') #4 .../wp-admin/index.php(115): require_once('/home/tmdsites/...') #5 {main} thrown in .../wp-content/themes/panoramic/functions.php on line 204

This issue just cropped up for a client using this theme as well. Looking for a fix asap.

There are often photos on posts and pages that users would want to be able to exclude from having the pinterest icon show up.

A few useful options this otherwise excellent plugin could desperately use would be a way to exclude the feature at a per-image level, as well as be able to enable/disable at a per page/post/category/taxonomy/conditional level. Also useful would be able to use this function on Custom Post Types.

OP. You can hide the PIN yourself with CSS albeit, it’s a bit obnoxious.

Just need to target the page or HTML element you want to remove the pin icon from and use a fuzzy CSS Selector like so:

.home span[class^="PIN_"] {
	display: none !important;
}

Still waiting on this – is it out yet?

I’m also looking for a similar answer – essentially a “get value from previous field / same row” call. Any luck?

likewise on the fontside in the woocommerce store pages i’m seeing:
Warning: explode() expects parameter 2 to be string, array given in wp-content/plugins/custom-taxonomy-order-ne/taxonomies.php on line 167

So i’ve managed to answer my own question – and the answer is outside of the plugin, and just uses WP calls. But for anyone looking to accomplish a similar redirect here’s what i’ve got.

<!-- Already logged in redirect -->
<?php
$current_user = get_currentuserinfo();
if ( is_user_logged_in() ) {
	wp_redirect( home_url('/client/'. $current_user->user_login .'') ); exit;
	} else { ?>
<!-- end Redirect-->

Also experiencing this on Client site – all comments being blocked with the following response: ERROR: Spam bot detected. Your comment was blocked from being posted.

Anyone find a fix for this yet? Currently plugin is unuseable.

Thanks Jonah – interesting issue here though:

I removed the old events/ folder from my template – and created a new one with the single.php template from views/ – and i’m experiencing the same issue…. template stalls from loading after the event title.

If i leave the templates in views/ they work fine.

Any suggestions?

update on my Theme issue – i deleted out the old /events/ custom styles folder in my theme and that cleared up most of the issues. Might be a good note to add in your install process, if you’re upgrading from 1.6x to 2.x – make sure to remove your old custom /events/ folder from your theme template.

I’m also experiencing a similar theme compatibility issue – the pre-20 version integrated fine, but my recent upgrade seems to cause the loading the page to fail after the title is displayed to any event, or event calendar related page.

If i load it inside another template the pages load fine so i know it’s not a plugin issue issue persay, but i’m curious what might be required of templates in 2.0+ version that wasn’t in the 1.6x version?

I’ve seen this with a few different hacked email accounts from various people. Not always from this plugin, but the same idea… [name].php?[image] must be a common exploit?

I also just received a link from a client’s Yahoo account (mass emailing) forwarding to a “friends.php” link inside a WP installation w/ Extended Comment Options.

OP – i’d recommend removing the full path to the image.php?miss164.jpg etc – if anyone here clicks that they may be exposed to malicious software.

To the plugin developer, i’d look into this