brightemo's Replies | WordPress.org

Forum Replies Created

Viewing 11 replies - 1 through 11 (of 11 total)

Forum: Plugins
In reply to: [Disable Blog] Archive custom post type

brightemo
(@brightemo)

5 years, 9 months ago

We have the same issue with version 0.4.9 and WooCommerce 4.5.1 on WordPress 5.5.1

The /shop/ page (i.e. ‘product’ CPT archive) was rendering with the blog layout rather than the shop layout.

Forum: Plugins
In reply to: [YITH WooCommerce Ajax Product Filter] Bug with 3.8.3 version
brightemo
(@brightemo)

6 years, 4 months ago
Hi @yithemes

The WeTransfer you linked to has been deleted/has expired.

Can you post the work around again please?
```
[23-Jan-2020 11:49:31 UTC] PHP Notice:  Trying to get property 'ID' of non-object in /srv/www/public_html/wp-includes/class-wp-query.php on line 3965
[23-Jan-2020 11:49:31 UTC] PHP Stack trace:
[23-Jan-2020 11:49:31 UTC] PHP   1. {main}() /srv/www/public_html/index.php:0
[23-Jan-2020 11:49:31 UTC] PHP   2. require() /srv/www/public_html/index.php:5
[23-Jan-2020 11:49:31 UTC] PHP   3. wp() /srv/www/public_html/wp-blog-header.php:16
[23-Jan-2020 11:49:31 UTC] PHP   4. WP->main() /srv/www/public_html/wp-includes/functions.php:1255
[23-Jan-2020 11:49:31 UTC] PHP   5. WP->query_posts() /srv/www/public_html/wp-includes/class-wp.php:731
[23-Jan-2020 11:49:31 UTC] PHP   6. WP_Query->query() /srv/www/public_html/wp-includes/class-wp.php:614
[23-Jan-2020 11:49:31 UTC] PHP   7. WP_Query->get_posts() /srv/www/public_html/wp-includes/class-wp-query.php:3413
[23-Jan-2020 11:49:31 UTC] PHP   8. apply_filters_ref_array() /srv/www/public_html/wp-includes/class-wp-query.php:3160
[23-Jan-2020 11:49:31 UTC] PHP   9. WP_Hook->apply_filters() /srv/www/public_html/wp-includes/plugin.php:249
[23-Jan-2020 11:49:31 UTC] PHP  10. YITH_WCAN_Frontend->the_posts() /srv/www/public_html/wp-includes/class-wp-hook.php:288
[23-Jan-2020 11:49:31 UTC] PHP  11. is_shop() /srv/www/public_html/app/plugins/yith-woocommerce-ajax-navigation/includes/class.yith-wcan-frontend.php:123
[23-Jan-2020 11:49:31 UTC] PHP  12. is_page() /srv/www/public_html/app/plugins/woocommerce/includes/wc-conditional-functions.php:32
[23-Jan-2020 11:49:31 UTC] PHP  13. WP_Query->is_page() /srv/www/public_html/wp-includes/query.php:574
```
Forum: Plugins
In reply to: [Social Media Auto Poster - Schedule & Publish to Buffer] ACF/Custom field support

Thread Starter brightemo
(@brightemo)

7 years, 8 months ago

https://www.wpzinc.com/documentation/wordpress-buffer-pro/changelog/

Solved for pro version already.

Author (via Email) says fix for free version will be out within a month.

Forum: Plugins
In reply to: [Advanced Access Manager – Access Governance for WordPress] Slight Conflict with Woocommerce
brightemo
(@brightemo)

9 years, 2 months ago
My guess is that because the ‘Access’ box you are adding has the same classes as the description box; that some ~~WooCommerce~~ Yoast SEO javascript is getting confused and modifying both…

Application/Backend/phtml/term-metabox.phtml
```
<tr class="form-field term-description-wrap">
    <th scope="row"><label for="description">Access</label></th>
```
Probably the term-description-wrap class.

—

Don’t think this has anything to do with WooCommerce; same thing happens on the Post category term edit page.

—

Okay just did a fresh WordPress install. The problem is between AAM and Yoast:

https://github.com/Yoast/wordpress-seo/blob/baaf22d02b9024a4528fa118a8829c01d08b570e/js/src/wp-seo-term-scraper.js#L44

Should be easily fixed by changing the term-description-wrap class in term-metabox.phtml
- This reply was modified 9 years, 2 months ago by brightemo.
Forum: Plugins
In reply to: [Advanced Access Manager – Access Governance for WordPress] Slight Conflict with Woocommerce

brightemo
(@brightemo)

9 years, 2 months ago

Confirming we have the same issue.

Deactivating AAM removes the duplicated description box on the WooCommerce category edit page. (/wp-admin/term.php?taxonomy=product_cat&tag_ID=XXX&post_type=product).

AAM Version 4.5
WC Version 2.6.14
WP Version 4.7.3

Forum: Plugins
In reply to: [Campaign Monitor for WordPress] jQuery included twice breaks other plugins/code
Thread Starter brightemo
(@brightemo)

9 years, 3 months ago
If this plugin needs jQuery 2 (over whatever is included in WordPress) then you could provide a local (rather than CDN) copy of jQuery 2 modified; with something like

window.jQuery2 = jQuery.noConflict(true);

at the end of the file. (The true flag releases the jQuery object as well as $)

Then modify this plugin to only use jQuery2() whether directly or via aliasing
```
(function($){
    $('#example').toggleClass('example');
})(jQuery2);
```
That would ensure that this plugin is compatible with as many other WordPress plugins as possible I think.

Example
- This reply was modified 9 years, 3 months ago by brightemo.
Forum: Plugins
In reply to: [Campaign Monitor for WordPress] jQuery included twice breaks other plugins/code
Thread Starter brightemo
(@brightemo)

9 years, 3 months ago
Okay so, yes, sorry, in theory you are right.

However the problem we are having is that:
1. jQuery (included with WordPress) is loaded: Populates global jQuery
2. jQuery Flexslider (from a ‘WordPress Plugin A’) is loaded: Adds function to global jQuery
3. jQuery (include with this plugin) is loaded: Overrides jQuery global
4. ‘WordPress Plugin A’ tries to call jQuery.flexslider in <body>, but it doesn’t exist
Example: One jQuery
Example: Two jQuery
Forum: Plugins
In reply to: Woocommerce upgrade to 2.4. forgets variations

brightemo
(@brightemo)

10 years, 8 months ago

Right so I seem to have found whats broken in my install…

Some _product_attributes are stored as a serialized string of a serialized array.

e.g.
s:240:"a:1:{s:22:"vertical-or-horizontal";a:6:{s:4:"name";s:22:"Vertical or Horizontal";s:5:"value";s:45:"Vertical Broadstripe | Horizontal Broadstripe";s:8:"position";s:1:"1";s:10:"is_visible";i:0;s:12:"is_variation";i:1;s:11:"is_taxonomy";i:0;}}";

Instead of
a:1:{s:22:"vertical-or-horizontal";a:6:{s:4:"name";s:22:"Vertical or Horizontal";s:5:"value";s:45:"Vertical Broadstripe | Horizontal Broadstripe";s:8:"position";s:1:"1";s:10:"is_visible";i:0;s:12:"is_variation";i:1;s:11:"is_taxonomy";i:0;}};

I have no idea how this happened, but it breaks the wc_get_product_variation_attributes function completely (as you’d expect).

Forum: Plugins
In reply to: Woocommerce upgrade to 2.4. forgets variations

brightemo
(@brightemo)

10 years, 8 months ago

Okay so scratch my last post, the stuff is there, my files do match the GitHub, variations still broken though.

Forum: Plugins
In reply to: Woocommerce upgrade to 2.4. forgets variations

brightemo
(@brightemo)

10 years, 8 months ago

Looking at the WC GitHub, this seems to be a known and fixed bug that hasn’t been pushed out to the wild yet….

https://github.com/woothemes/woocommerce/commits/79ee83e0d00919ff10fd312d77bab39eb55047f3/includes/class-wc-product-variation.php

If you look at the commit log from Jun 11, 2015 onwards, you’ll see a few entries mentioning fixing it.

“Attempted bw compat by comparing sanitised text to real text”
“Add version check to prevent pre-2.4 logic kicking in when not needed”

Any idea why this isn’t in the live version? My class-wc-product-variation.php says @version 2.2.0 at the top….

Forum: Plugins
In reply to: Woocommerce upgrade to 2.4. forgets variations
brightemo
(@brightemo)

10 years, 8 months ago
We are having the same problem…

It seems to be the way that the attributes were stored in the database, but are now stored differently:

wp_postmeta:
```
meta_key | meta_value
attribute_custom-attr-name | custom-attr-value-1 <-- old
attribute_custom-attr-name | Custom Attr Value 1 <-- new
```
The only way we’ve managed to fix this is manually going through remapping the products, but are in the same situation as yourself, having more products than sensible to attempt this.

Viewing 11 replies - 1 through 11 (of 11 total)