Forum Replies Created

Viewing 15 replies - 1 through 15 (of 79 total)
  • I have the same thing but it’s reporting line 80:

    Fatal error: Call to undefined method WPV_Settings::get_instance() in /home/handsome/public_html/wp-content/plugins/types/library/toolset/toolset-common/user-editors/medium/screen/content-template/frontend.php on line 80

    This seems to be the result of an update and right now it’s breaking all custom posts templates.

    I’m on WooCommerce 2.4.14 and I’m seeing #38; as well. It’s a badly encoded &, but it’s also unnecessary. The params before #38; are all correct, as are the results.

    OAuth classes are often copy and pasted into a plugin without regard for other plugins that could be declaring the same class. This is what WC Vendors did and it’s what YITH does too. You can change the class declaration in /OAuth/OAuth.php on line 139 to check for class existence first with:
    if (!class_exists('OAuthSignatureMethod_HMAC_SHA1'))...

    That risks the other declaration being different and causing an issue but that’s unlikely. That worked for WC Vendors. You’ll probably see similar errors for other similarly named classes. Just keep adding the above conditionals to check for existence before declaring.

    The proper solution in my opinion is name spacing your classes, or declaring them within another class by the name of the plugin.

    My theme (oxygen by laborator) and another plugin (wc vendors) both have copy pasta OAuth class files. They’re both very important to the site. I had to go through and wrap reach declaration in an if class_exists condition to get billing code to work. Pretty annoying. I’ve asked wc vendors to namespace their billing code class declarations. It’s billing code after all.

    If code inside these similarly named classes don’t agree, it could really screw things up. Couldn’t they all be declared in one unique class by the name of the plugins?

    Ok, so after more testing, it seems the version of imagemagick is irrelevant. The problem is with an imagemagick PHP API called magickwand. When enabled, images over 1MB cause an infinite loop. A newer server with the same host doesn’t seem to be affected by the issue with magickwand enabled so it seems to be a conflict of certain combinations of versions.

    We could be talking about totally separate issues, but there’s a chance your experience has the same cause as mine.

    I’ve been working with my host for a few days, created some sandboxes, did some diffs and we believe we’ve narrowed it down.

    ImageMagick 6.8.8-7 is an older version that apparently has some security concerns, however it’s the version that isn’t afflicted with what appears to be an infinite loop. We saw the issue with PHP 5.3 and 5.4, as well as WP 4.2.4 and 4.3.

    ImageMagick 6.9.2-1 is the newer more secure version which runs a loop and hits max_execution_time several times. It seems for some people this causes an image upload failure. For me it just hangs for about 2 minutes before eventually showing the uploaded image.

    Changing PHP settings to use GD instead of imagick “fixes” the issue (by circumventing it), but this isn’t an option for shared hosts. The host doesn’t consider downgrading imagick an option due to security concerns so now I’m looking for a way to disable imagick through WordPress settings or php.ini. The fastest way around the issue would just be switching to a VPS, which I may end up doing.

    I have a long execution time setting and uploads over 1mb are hanging for about 2 minutes. I’m also already on php 5.4. Do you guys mind sharing your phpinfo() url if you have this issue fixed?

    Does anyone know if you use remove_meta_box for custom fields, if that stops the associated slow query without having to modify core files?

    It looks like there could be a very slow query with WooCommerce:

    https://wordpress.org/support/topic/woocommerce-extremely-slow-after-wordpress-42-update?replies=64

    The error is:
    Fatal error: Cannot redeclare class OAuthSignatureMethod_HMAC_SHA1 in /home/wedding-recyclejail/home/wedding-recycle/public_html/wp-content/plugins/yith-woocommerce-social-login/includes/hybridauth/Hybrid/thirdparty/OAuth/OAuth.php on line 139

    This doesn’t seem to be an error I can do anything about on the Twitter side of things. Unless it is, in which case let me know what I can change.

    Remember that if there’s an update released for Hashbuddy, it may override this change and break your hashtag urls. You could change the name of the plugin so it doesn’t see updates for it anymore, or you could try getting to the bottom of the BP_ACTIVITY_SLUG issue. I still don’t know why it wasn’t listening to the BP page settings or being set when I deliberately set it.

    I declared support in my child theme to override issues I was having with the default styling, but I’m finding it difficult to get the styling right. The video preview for examples drops in an iframe which is 1500 x 844. I’m running a fork of the plugin so I have no problem modifying it more, but those dimensions are still proving hard to locate and change.

    Another issue: I have a plugin called Hashbuddy which runs a filter to insert a link for #hashtags. It works fine except on activity plus posts. It could be an issue with Hashbuddy or this plugin is somehow circumventing that filter.

    I made a gist here:

    https://gist.github.com/archonic/e49de88b4619f181f56d

    With the plugin installed and activated, try replacing /wp-content/plugins/hashbuddy/includes/hashbuddy.php with that file, but remove

    . 'dashboard'

    around where the comments say to do that.

    I came back to this and tried to set the define BP_ACTIVITY_SLUG in my child theme’s functions.php and no luck. Unfortunately editing the plugin was all I could do to get it working. Rename the plugin and change the name of the folder it’s in so you’re working with your own plugin which won’t update.

    In your case, if you homepage is your activity feed, change line 10 in /includes/hashbuddy.php to this:

    $activity_url = trailingslashit( get_bloginfo(‘url’) );

    No need to concatenate a slug to the url if it’s the homepage.

    Trailing slash it should just add a slash at the end – but do whatever works!

Viewing 15 replies - 1 through 15 (of 79 total)