Can you paste your theme into AI and see if it can tell you why is that? My guess would be that you have something wrong in your print stylesheet of custom theme
What if we do like to author by hand. We have custom logic on invoice that cannot be achieved by using AI, or requires much more time training AI than manualy write code. Will there be so reference for themes. Exposed data, using custom fields, data structures, etc… With Theme Enhancer we had data variables rendered at the bottom. What about now ?
What about build in ones as reference and/or starting point. Reference and documentation is what always developers are/were asking for all new things in manager.
Using Perplexity Pro with ChatGPT 5.4. Copy/Pasted skeleton. Asked to create minimalistic black and white invoice. Returned code pasted into theme. Not working at all.
Can we have a tutorial, or at least some pics with step by step, and produced code for reference.
Initially I struggled. Although I am familiar with HTML, CSS and java script I found it easier to ask Chatgpt (we have business edition and I used the Pro-Extended agent). Initially I just got a blanc screen when using @Hazem suggestion. However when adding that it needs to use OpenAPI spec it all worked perfectly well. If anything this is an excellent improvement to Manager. Liquid was giving issues but this is excellent. So if having issues using AI tell it to use OpenAPI spec. If it can not use another AI.
I’m thinking to just include OpenAPI spec in skeleton theme. That will eliminate half of the issues. The second half of the issues can be eliminated by simply Manager checking theme starts with <!DOCTYPE html> which would indicate you are really pasting the full HTML code, not just portion of it. AI will often give you just changed code block to save on tokens. This can be confusing.
Other than these two recurring issues which can be solved, it works very well.
I would ask for users to share Prompts and if they used just skeleton provided. Ready, nice looking themes also acceptable to start from, because probably this iteration is hating me, or I ask too much. I cannot get a decent “normal” invoice look from AI. Theme Enhancer was MasterGPT 10.0 for this invoices I get right now. I wonder how new users, that have no previous theme experience, or saved themes from previous iteration, how will they get simple useful invoice.
Where did you find this info? Where to find all data field reference? For build in ones, and also for custom fields inside business (Second name, additional info needed, etc) , invoices (some added custom fields, etc), …
Hi, the Classic custom field images doesnt work even with using HTML code using ChatGpt, please help
Since Images in Classic Custom Field doesnt work. i have to manually update all of Sales Invoice record to have Image on new Custom Field. imagine manually clicking all 1000 records just to have the Image, since Batch update doesnt update Images unlike Classic Custom fields
What I usually do to help the AI understand my requirements is to provide it with:
– An image or draft layout of the invoice
– The skeleton structure from Manager
– The log data received from the API
and chat Hi, please help me create a template like the image I provided.
After that, it’s just a matter of making adjustments.
Here’s your request rewritten in English, keeping the technical details intact:
Create a complete invoice.
Create new custom themes, and add the following line:
console.log(JSON.stringify(data, null, 2));
just before:
renderDocument(data);
Use the custom themes in the invoice.
When you view the invoice and inspect the browser, you should see the logged data in the console. Provide that data to the AI.
Alternatively, a more effective approach: if you already have older Custom Themes, you can provide that data to the AI and ask it to refactor.
Provide the old Custom Theme and the new Custom Theme skeleton.
Ask the AI to rebuild the theme so that it produces the same output as before, but now the data is obtained from the API.
@Mabaega giving AI example of the data it can receive gives even more context. I think I could make JSON data visible when editing the custom theme from specific document. This would avoid console.log step.
This is based on the ‘RAW HTML theme’. The view follows any style changes like expected (eg. body font size value change), it is the PDF that doesn’t follow. I cannot seem to influence that. Still inestigating.
There are no issues with the fonts. Everything remains consistent across the on‑screen view, print preview, and the final PDF. All outputs look identical.
In this sample, I used fonts served from a CDN, and they all rendered consistently.