Long description not editable (mapping?)
The support doesn work on Saturdays and Sundays, so some Friday requests can be answered on Monday. If you have problems with registration ask help on contact us page pleaseIf you not got email within 24~36 business hours, firstly check your spam box, and if no any email from the support there - back to the forum and read answer here. DO NOT ANSWER ON EMAILS [noreply@pluginus.net] FROM THE FORUM!! Emails are just for your info, all answers should be published only here.
The support doesn work on Saturdays and Sundays, so some Friday requests can be answered on Monday.
Hello,
Product Short description editing works perfectly with binding (so I am seemingly not the problem ;-) ), however (Long) Product description (named"Description"?), actually the same...(?), does NOT.
(Long) Product description (named"Description") shows also the"Content" button in the list, but it contains my DIVI's page structure, not the description.
And when I deleted this and replaced it with my description text in BEAR, the description was also NOT edited/changed in the WP/WOO standard product edit view/field. Also in the bulk edit mode"Description" was not updated.
Thus... looks very much like a wrong field mapping? But I cannot find another field in"Settings" that could be the REAL"(Long) Description" field...
Thank you very much for your help!
Hello
I just did little test with BEAR and field description and long text and all is ok, so lets resolve issue why its doesn work on your site. Firstly I can suggest you deactivate any cache plugins, because this is can be a reason, check, and if all is ok tell me please here what cache plugin is installed on your site. If after disabling cache plugin still issue there, disable all plugin except BEAR and WooCommerce and check, I think all will be ok, so one by one enable another plugins and check to define the plugin with the conflict. About results please give me know in this support request branch
...I found out the following, hoping this helps to solve the issue:
- I replaced DIVI Theme (Builder built in version) with the WP Twenty-24 theme and found no issues then also with BEAR.
Meaning: if updated in BEAR and then checkd in te WP product edit view, the field is updated correctly AND immediately.
If DIVI is activated, the following happens (always field"(Long) Description" only !!) to compare (all tested with"Binding" option (only):
- BEAR shows immediately the changed field content.
- However, with DIVI activated, the WP product edit view however does NOT, that shows the old content from before.
- At first I thought there could be a time lag, maybe caching ralated (NO active caching plugins installed, DIVI only and several others most probably not relevant),
because: on a second try a few minutes - edingt again in the WP edit view - it was correct also there, then. - HOWEVER - strange thing:
It does NOT SEEM to be a time lag, but it seems instead that opening the WP edit view for a SECOND time only does the update job!? (BEAR editing in this case with no effect until the SECOND time in WP edit view after that... which is then much confusing of course + useless + tons of failures/mistakes in editing/checking...) -
In other words: While changes with the Twenty-Four Theme do apply immediately and correctly to the original WP field, with DIVI I need to go TWO times in this WP edit view to get the changes IF these have been made with BEAR. And only then they are also displayed in the frontend, of course (DIVI gets it in real time from the WP original field... so the problem ist the (immediate and/or correct) update of this field with/after BEAR editinf). - At least it seems to be not a time lage issue, maybe caching INSIDE DIVI or maybe conflicting actions or something like that... you will know or imagine much better I guess...
Remember that this problem does NOT appear with e.g the field"Short Description"!?
To me it seems really a little bit strange to guess the concrete reason for this behaviour, but I hope you can figure out and solve it? (Maybe also together with the DIVI team?)
Thank you!
Hello
Thank you for your great description, I just created task to dev department to investigate this incompatibility. This will take time, so please be patient. Also please if you subscribed to DIVI service create task with question about how this can be resolved, maybe they will give you good receipt more quickly as the know their code better. Thank you ...
I tested over the day with the DIVI Team. So far our conclusions: The problem seems to appear only IF"Use the DIVI Builder" is activated in the"Edit Product" view in the backend (at least) (so that DIVI loads there).
If this is off or reset to"Do not use the DIVI builder (of course all related content lost then!)", if works (again).
Next remaining question is why THEN (only then also) BEAR ist showing DIVI code in the field"Description" instead of an empty field (while the same field in the Edit Product view is empty).
Maybe you have also an idea where to search or a hint for us.... So far our research news.
I add a short video from the DIVI Support Team:
It shows PART 1:
1. Create a new product, all empty except the Title. Leave also the field"Description" empty.
2. Activate"Use the DIVI Builder"
=> In BEAR, instead of the empty field"Description", you will find DIVI layout code.
https://go.screenpal.com/watch/cZj2YwV9vj2
--
PART 2 - NOT in this video:
If you then edit/change the same field"Description" in BEAR, you have to go TWICE into the normal WP"Edit Product" view to see the field update (at first check/edit it remains empty and is also not shown in the frontend).
--
If"Use the DIVI Builder" in standard the Product Edit view is disabled, all this does not happen and all seems at least to be fine.
Overall, we both assume that the issue is probably more caused by your plugin, hoping that this feedback helps you to solve the issue.
I would forward your notes to the DIVI team as well (or you could check directly with Faisal from ET). So I think we will get it done...
Thank you again also for your help!
Hello
Thank you for your help, this should help in our investigation ...