About this plugin
JHMG Converter For Bricks to Divi 5 reads a Bricks Builder page’s stored settings — never its rendered
HTML — and writes a new Divi 5 post from them, leaving the original Bricks page untouched. It supports
converting a page already on the site, or a Bricks export uploaded through the admin screen.
Every conversion produces a report of what was carried over, what could not be mapped to a Divi
equivalent, and any global variables or colours that could not be resolved, so nothing is silently
dropped or guessed.
External services
This plugin makes no request to any third-party service. Converting a page reads data already stored on your own site, and
nothing is sent anywhere during a conversion. The pages it creates, however, can contain links and embeds that your visitors’
browsers follow, so they are listed here.
Social share buttons (converted Bricks “Social sharing” elements). Each share button becomes a link to the network’s own
share page. Nothing is sent when the page loads; when a visitor clicks a button, their browser opens the network with the
page’s address, title and, for some networks, the page’s excerpt and featured image address in the link, so the network can
prepare the post. The networks are Facebook, X (Twitter), LinkedIn, WhatsApp, Pinterest, Telegram and VK. Each network also
receives the usual request data from the visitor (IP address, browser details and any cookies it has set).
- Facebook: https://www.facebook.com/terms.php and https://www.facebook.com/privacy/policy/
- X (Twitter): https://x.com/en/tos and https://x.com/en/privacy
- LinkedIn: https://www.linkedin.com/legal/user-agreement and https://www.linkedin.com/legal/privacy-policy
- WhatsApp: https://www.whatsapp.com/legal/terms-of-service and https://www.whatsapp.com/legal/privacy-policy
- Pinterest: https://policy.pinterest.com/en/terms-of-service and https://policy.pinterest.com/en/privacy-policy
- Telegram: https://telegram.org/tos and https://telegram.org/privacy
- VK: https://vk.com/terms and https://vk.com/privacy
YouTube and Vimeo (converted Bricks “Video” elements). The video’s address is saved in a Divi Video module. When the page
is shown, Divi embeds the video through WordPress’s oEmbed support: your site may ask YouTube or Vimeo for the player, and a
visitor’s browser then loads the player from them and sends the usual request data (IP address, browser details and any cookies
they have set). Pages without a video make no such request.
- YouTube: https://www.youtube.com/t/terms and https://policies.google.com/privacy
- Vimeo: https://vimeo.com/terms and https://vimeo.com/privacy
Google Maps (converted Bricks “Map” elements). The map’s address or coordinates and markers are saved in a Divi Map module.
When a visitor views the page, Divi loads Google Maps, which receives the usual request data from the visitor (IP address,
browser details and any Google cookies). Pages without a map make no such request. Divi’s Map module uses the Google Maps API
key set in Divi’s own settings.
- Google Maps: https://developers.google.com/maps/terms and https://policies.google.com/privacy