gambitph / Stackable

Page Builder Blocks for WordPress. An Amazing Block Library for the new WordPress Block Editor (Gutenberg).
https://wpstackable.com
GNU General Public License v3.0
329 stars 62 forks source link

[WPML] Custom Stackable button becomes untranslateable on WPML's translation editor #2656

Open andeng1106 opened 1 year ago

andeng1106 commented 1 year ago

Describe the bug Stackable button block becomes untranslatable (not detectable) when there's a Blocksy custom font & border styling. Resources: https://drive.google.com/drive/u/0/folders/1OsMJtEzA-_kzrzxGA0s9vVxEzNZph8KN

Stackable version used: Premium 3.7.2 WPML Version used:

Assumptions:

Reference: https://secure.helpscout.net/conversation/2227585384/20452?folderId=2526706

To Reproduce Steps to reproduce the behavior:

  1. Activate Blocksy Theme
  2. Activate these plugins:
    • Blocksy Companion (Premium)
    • WPML Multilingual CMS: Version 4.6.3
    • WPML Media: Version 2.7.2
    • WPML String Translation: Version 3.2.5
    • Stackable 3.7.2 (Premium or Free)
  3. Add a new page
  4. Add this block code: custom button blocks.txt
  5. Translate page using WPML Translation Editor (Page > Translate this document > WPML Translation Editor > Select a language)
  6. After redirected to WPML Translation Editor, check if all the buttons in Step 5 are translated (Actual behavior (issue): Can only translate buttons Border Custom 1 & Border Custom 2

Expected behavior

Screenshots Border Custom 1.2 & Border Custom 2.2 is not translatable

https://user-images.githubusercontent.com/103395655/236108719-5870b119-d911-4758-bf4b-6141ae329386.mp4

Removed the styling for Border Custom 2.2, I removed the styling then it becomes translatable

https://user-images.githubusercontent.com/103395655/236108805-b28a9e86-8091-4612-87b9-a39a62a50835.mp4

andeng1106 commented 1 year ago

issue doesn't occur anymore but for monitoring after 3.8.0 release

andeng1106 commented 1 year ago

Confirmed as fixed for 3.8.0 release.

andeng1106 commented 1 year ago

This issue was opened up again. See: https://secure.helpscout.net/conversation/2227585384/20452?folderId=2526706