Skip to main content

Divi Community (FREE)

#Divi Related

Join The KrafterPRO Beta Testing Program.

Thanks for helping test KrafterPRO before release. This beta touches Divi 5 global variables, presets, rollback snapshots, and reset tools, so please follow the rules below to keep your site safe and your reports actionable.

Rules (please read)
  • Staging/local only. Do not test on production.
  • Make a full site backup first (host backup or Duplicator/Updraft).
  • Keep Divi 5 active during testing.
  • If something goes wrong, stop and report before trying random fixes.
What you’ll test
  • Import preview and import execution (combined + split JSON)
  • Replace vs Merge behavior
  • Exclusions (including brand slots)
  • Export correctness + re-import roundtrip
  • Rollback snapshots + restore
  • Reset tools + rollback safety
  • Style guide refresh + “Save as PDF”
  • Downloads (bundled JSON assets)
  • Admin navigation (Dashboard tabs + Help/System/Licence submenus)
  • Licence/Shop gating behavior (policy validation)
How to run the test

  1. Confirm environment: WordPress 6.x, PHP 8+, Divi 5 active, KrafterPRO active.

  2. Open these menu items and confirm they load correctly:

    • KrafterPRO → Dashboard
    • KrafterPRO → System
    • KrafterPRO → Help
    • KrafterPRO → Licence

  3. Import: preview a known-good combined JSON.

  4. Import: run Merge on a small fixture; confirm expected changes only.

  5. Export: export JSON; confirm it opens as valid JSON.

  6. Rollback: restore the snapshot from before the import.

  7. Style guide: Refresh from site; Save as PDF and confirm colors show in print preview.

  8. Downloads: download both bundled JSON files and confirm they open.

Paste ALL bugs and errors here.

Here is the link to become a beta tester.

Join The KrafterPRO Beta Testing Program.
  • 1 like
  • 5 comments

Giovanni Scafaro

Il mio rapporto Beta Test KrafterPRO – Ostacolo Licenza e Log Attività

Ciao Mak,
Spero che tu stia bene. Un doveroso saluto a tutta questa splendida comunità di amici che condividono questa missione.
Nel dare inizio ai crash-test. mi sono imbattuto in un piccolo intoppo tecnico.
Ho preparato l’ambiente di test seguendo alla lettera il Protocollo di Sicurezza. Ho scelto di lavorare in Locale (tramite LocalWP) invece che in staging o produzione per un motivo di "Misura" e protezione: voglio poter testare ogni limite di KrafterPRO e Divi 5 senza rischiare di influenzare la stabilità dei server e causare improbabili impatti indesiderati, ma purtroppo sempre possibili.

Stato attuale del Laboratorio:
Ambiente: WordPress 6.x su LocalWP.
Motore: PHP 8.2.27 / Nginx.
Core: Divi 5 ultima versione 5.3.1 installato e attivo.
Sistema: KrafterPRO Agency Beta (v2.0.66) installato.
Rilievo System: Tutto "Verde". Memoria e tempi di esecuzione sono perfettamente calibrati.

L'Ostacolo:
Ho controllato per filo e per segno ogni angolo digitale: la fattura #INV-2356, le email ricevute, il mio account sul portale e persino la transazione PayPal. Purtroppo, non sono riuscito a reperire il numero di licenza per attivare le funzioni Pro nel mio ambiente di test.
Dimmi come attivare la licenza. Senza la chiave, non posso procedere con i test di Import/Merge e la verifica della Style Guide che mi avevi chiesto.

Domanda Operativa:
Oltre a chiederti dove posso recuperare la licenza, volevo sapere se preferisci che continui a comunicarti i progressi e i rilievi tecnici direttamente qui su questa piattaforma o se preferisci un altro canale.

In attesa della "chiave d'oro" per procedere, ti auguro un ottimo lavoro.

Avanti a tutta forza!
Giovanni Scafaro

Giovanni Scafaro

KrafterPRO Beta Test Final Report (v2.0.66) dated April 26, 2026

To: Mak
Subject: Technical Survey, Test Summary, and "Triple Slot" UX Proposal

Hi Mak,
After an intense crash-testing session in a local environment (LocalWP + Divi 5), here is a summary of the findings. The system is solid. I've identified some areas where we can make navigation even smoother and more secure.

  1. Operational Summary (What I did):
    Environment: Clean installation on LocalWP with Divi 5 (Alpha).
    Import/Merge: The KrafterPRO engine correctly received the variables (50 colors, 2 fonts, 78 variables, 269 presets).
    Visual Builder: Test passed. Imported colors and fonts appear correctly in the Divi 5 presets, allowing for immediate customization of modules.
    PDF Style Guide: Successful generation. The document is professional and reflects the brand's identity.
  2. Technical Findings (The "Small Stumbles"):
    PDF Light Logo: In the PDF, the "Light" logo (white/light) disappears into the white background of the page. A colored preview box or a neutral background for this section in the PDF would be helpful.
  3. The Proposal: The "Three Slots" System
    To optimize agency time and reduce confusion for new users, I propose evolving the KrafterPRO interface with three distinct, colored "Drop" areas, which automate the connection with Divi Theme Builder without changing pages:
    🟣 PURPLE Slot (Variables): For the variables.json file.
    🟡 YELLOW Slot (Presets): For the presets.json file.
    🟢 GREEN Slot (Theme Builder): A new slot dedicated specifically to the Theme-Builder-Template.json file.

The Idea: By uploading the file to the green slot, KrafterPRO should automatically "inject" the templates into Divi's Theme Builder via an internal process (if possible). This would provide the user with complete security: each file has its own colored home, and there's no need to exit the plugin to complete the setup.
As I often say: "Organizing beauty means making it accessible to everyone."
Full steam ahead!

Bryan

Okay, perhaps it's my newness to all this. I have downloaded Krafter Pro Beta zip file. Now, how do I install it on my staging site? Is it installed as a plugin? Or, do I need to unzip and install individual components?

Thanks

Mak .

Bryan Hi Bryan. Install it as a plugin, do not unzip it.

Kevin Waite

For simplicity, would it make any sense to have a single drop zone for files? Parse the file via programming logic to determine whether it's a variables, presets or themes json file. Make the plugin do the thinking :-). Love what I'm seeing so far!