Collin Condray

I don’t know if this is related but a client of mine had their site go down with the following error:

Fatal error: Can’t use function return value in write context in /usr/www/users/sitename/wp-content/plugins/svg-support/svg-support.php on line 45

When we disabled the plugin, the site came back up. Just FYI.

We’re hosting with WP Engine which has dedicated WordPress hosting. Is there anything I can tell them to change on their end that might help mitigate this?

I’ve got a temporary fix for this. Edit the miniAudioPlayer.php file and change line 139 from:

if (empty($miniAudioPlayer_active_all)) {$miniAudioPlayer_active_all = “true”;}

to

if (empty($miniAudioPlayer_active_all)) {$miniAudioPlayer_active_all = “false”;}

When you uncheck the “Apply to any .mp3 file link” box, it looks like it sets the database value to empty instead of false. This change makes sure that when the database value is set to false or it’s empty, the player is not used.

Our client has asked for this functionality from this plugin again. Is there any way to specify multiple statuses in the shortcode? Are there different shortcodes I can use to achieve this effect? If so, what are they and what is their syntax?

Are you referring to another shortcode within the plugin or will we have to create our own shortcode? If there is another shortcode in the plugin, can you tell me what the syntax of it is?

Thanks,

Collin

Thanks for the reply however, I’m not sure I explained things correctly. I wasn’t referring to the display parameters of the shortcode. Those are working as expected.

My question was about the custom taxonomy part of the shortcode parameters. I have a Status taxonomy that shows the property’s current status (Available, Active, For Rent, etc.). I would like to either show all properties that have no status taxonomy set. If that is not possible, I would like to bo able to set multiple status to be displayed.

I don’t think this is possible based on the code starting at line 47 of includes/shortcode.php. It just looks like it handles a single parameter as described in the Simple Taxonmy Query as describe the WP docs (https://codex.www.ads-software.com/Class_Reference/WP_Query#Taxonomy_Parameters). Do you recommend any other way of specifying multiple taxonomy values?

Thank you for your help.

I removed the query string from the /wpmovielibrary/assets/fonts/wpmovielibrary/style.css file and that seemed to have done the trick. Thanks for the fix and for the great plugin!

I think I’ve come up with a fix that gets rid of the error message.
Starting at line 98, of main_plugin_fields.php, replace it with the following code: https://pastebin.com/utdc4ztf. It makes sure that the foreach array is actually an array. I don’t know what this does to the functionality of the plugin but at least it gets rid of the error message.

The way we have it is that taxes are completely disabled in wpec and the ZIP code level tax rates are set up in PayPal. The taxes will show up after you put in your credit card and billing address. They are not transmitted back to wpec via IPN. Can you try that combo and see if it works for you?

I forgot to mention that this change needs to be made in the /wp-e-commerce/wpsc-merchants/paypal-standard.merchant.php file for those who are having the same problem until the fix.

Great! Looking forward to the update.

You might be running into a shortcode conflict. We use Woothemes and those themes have a [fblike] shortcode that was overriding this behavior. If this is the problem, then you’ll have to rename the shortcode. To do this, open the fbtab.php in the root of the plugin directory. Go to line 669 and replace the line with this:

add_shortcode('fbtablike','fblike');

then use the shortcode [fbtablike] instead of [fblike] and see if that fixes the problem.

I can see the main Highrise settings now in Gravity Forms 1.7.2 now but I can’t see it on the individual forms settings. Is that what you’re seeing too?

Here’s a possible fix for it: https://www.ads-software.com/support/topic/category-product-list-not-showing-all-items-possible-fix

It looks like common special characters like question marks and colons are working for me. I haven’t seen any character that completely gums up the work though.