Price returns 0 when added to cart.

I am sure the dev is working on ways to warn/avoid this issue.

Yes. In the next major version (which in fact will be Builderius, but you know it already if you follow our fb group) there will be truly global modules. Upon updating in one instance it triggers update all other instances across site. Overwrites will be clearly seen. Of course, you will still have to decide if you really want to overwrite it or it is the perfect time to create a new module. ??

Das verstehe ich nicht:

“Wenn Sie ein Produkt duplizieren, wird die Verknüpfung zu den Attributen instanziiert (eine symbolische Verknüpfung zur Option). Achten Sie darauf, diese Module nicht mit aktivierter Datenbank in einem duplizierten Produkt zu speichern, da Sie sie von instanziierter zu direkter Verknüpfung ?ndern und überschreiben / übernehmen vom Originalprodukt (Dies macht Ihr Originalprodukt unbrauchbar)”

Kannst du das genauer erle?utern ?

I do not understand that:

“When duplicating a product, the link to the attributes are instanced(a symbolic link to the option) be careful not to save these modules with DB on, in any duplicated product as you will change it from instanced to direct link, and overwrite/takeover from the original product(This renders your original product useless)”

can you explain that again

The modules that you create for a product (lets call it Product-A) needs a slug name which needs to be unique.(Lets call it cpo_length) When you save the module for the first time, with DB checked, it creates a global attribute(option), which is called cpo_length, which resides in the database.(the list you se in cpo-options on the wp-dashboard) At the sametime it also linked with the module (Se sync ID in module), The module now has control over that attribute/option.

When you duplicate a product(Product-B) with that module, it is now also linked to the same attribute/option: cpo_length_a, but as an instanced link. The copy process takes into account the origin of module option.

cpo_length_a is now working on both products.

If you open the module in Product-B and check the DB and press save, Product-B now recreates the link as if was the first time, reassigning a sync id, with no regard to product-A. product-A is no longer synced/attached/linked to cpo_length_a

If you need to change a module in Product-B after copying, make sure to rename the slug: cpo_length_b before you save to the db. This way the module creates a new unique option: cpo_length_b and linkes that to the module in product-B, without touching the original cpo_length_a. Remember to change the calculation form in product-b module, to use the new option: cpo_lenth_b

Hope that makes sense ??

next major version (which in fact will be Builderius, but you know it already if you follow our fb group)

Story of my life. Just bought your plugin yesterday, the same day I became aware of you ?? no clue you had a facebook page.

??
Yes, we do, it is called Builderians

Thanks for the good explanation. I’ll summarize again to check whether I understood correctly. When duplicating a module, the slug of the module gained by duplicating must ALWAYS be reassigned. As I noticed, the system warns you with an exclamation mark and suggests a new slug name.

But what happens when we duplicate an entire product? Do ALL slugs have to be changed in ALL modules?

we always have a problem with conditional logic. Although all options have been set correctly, the input fields are not displayed. can this also have the same cause?

I look forward to your short-term feedback

But what happens when we duplicate an entire product? Do ALL slugs have to be changed in ALL modules?

No. They are connected instances, they work already.

When duplicating a module, the slug of the module gained by duplicating must ALWAYS be reassigned. As I noticed, the system warns you with an exclamation mark and suggests a new slug name.

You need to be clear about your problem. Do you have issues with duplicating Modules or Products?

Dear Dev. could you perhaps make an update for the plugin, so that you issue a warning before people overwrite? It could be that you ask the user:
“Warning: you are about to Overwrite a global option.”
Give the user the option to Confirm overwrite, or to make new unique slug (based on either a +_1(in same module) or _”product-name”(If in a duplicate product))

• This reply was modified 4 years, 3 months ago by pandusen.