-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extended Print Text section character limit #172
Comments
The current limit is enforced on the client side. I don't know how much text you're trying to input, but there is a larger limit on the backend. Can you paste an example of how much text you're trying to add? It's also possible for the time being that you use the page inspector to override the limit on the text field in the client. This should let you add a larger amount of text. |
Haven't heard about a page inspector, not sure what that may be. As for an example, say you wanted to upload two sets of code that creates two tables, one using the Ajaba Form bonus and the Basic Renown templates that are now located in the common templates page in the wiki here. There is not enough character limit in the field to contain both sets of code. Me and Aaron have been getting as creative as we can stacking the code together to eek out as much programming logic and content as we can before reaching that limit. |
This is the example where Aaron was reaching the max character limit so he took out any returns or spaces where he could.
|
You should be able to drop the body and html tags too since this content will always be injected into an existing page. I've been doing tests trying to drop the limit and I haven't found a good way to do it. I'll keep trying though. I'm going to take this on as a target for the 0.8.5 release since it wasn't as straightforward as I'd hoped. |
We ran into a character limit in the Extended Print Text section while trying to create more complex tables and logic for the templates were creating and wanted to know if that can be increased or if it is a hard coded limitation.
The text was updated successfully, but these errors were encountered: