Skip to content
This repository has been archived by the owner on Mar 17, 2022. It is now read-only.

deactivate meta synchronisation #13

Closed
tolima opened this issue Oct 27, 2015 · 7 comments
Closed

deactivate meta synchronisation #13

tolima opened this issue Oct 27, 2015 · 7 comments

Comments

@tolima
Copy link

tolima commented Oct 27, 2015

Hi,
If I deselect all checkbox of a group (general, stock etc) of Meta list (in WooPoly Advanced Options) all the check box are reseted and re-checked.
Is there a way to deactivate meta synchronisation ?

@b-alidra
Copy link

Up

@tolima
Copy link
Author

tolima commented Nov 19, 2015

In src/Hyyan/WPI/Product/Product.php, function __construct()
comment new Meta();
to deactivate all syncronisation
It's not the solution but it work.

@b-alidra
Copy link

@tolima Thx

@hyyan
Copy link
Owner

hyyan commented Jul 30, 2016

It is part of the plugin job to sync meta , but you can control meta from the plugin options page , working perfectly with v0.27

@hyyan hyyan closed this as completed Jul 30, 2016
@hyyan hyyan self-assigned this Jul 30, 2016
@tolima
Copy link
Author

tolima commented Sep 14, 2016

It is part of the plugin job to sync meta

yes but if we don't want this part of the plugin ? Or if we don't want it on a whole group (general, stock etc) ?
I have the same problem with 0.28

@decarvalhoaa
Copy link
Contributor

I did a few tests and notice that indeed, if one unchecked the settings of an entire Group, after pressing Saving Changes, the settings boxes get re-checked. Apparently, if you only uncheck a few options, it gets saved ok. Still need to test if the fact they are unchecked really takes effect.

On this basis, I would say it is a valid bug.

Also, I would agree that it would be nice to have a button to uncheck/check an entire Group. This would be a feature enhancement.

If I find a little bit of time, I will try to fix it and propose a solution to Hyyan. Unfortunately, I have quite a lot of work right now, and can really promise a date.

@Jon007
Copy link
Contributor

Jon007 commented May 2, 2017

Closing - I can't replicate this on current versions.
According to change log, there was a related fix on Issue #51 in version 0.29

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants