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
Editor handling #1
Comments
Yes, editor options in the Options panel is the best option, I fixed it since my GS site has it's own editor options and it broke the wysiwyg. |
What sorts of options should be available?
Also, it might be possible to add a small CKEditor plugin that allows the admin to more easily embed a link to an existing product/category (but I don't want to get too ahead of myself here). |
Looks good, I'll test it tomorrow .. |
I've merged your changes into the master branch on the main repository, and I am going to merge v0.2 in soon. When that is done, update your master branch (as stated by the asterisk here), create a new branch for the changes you want to make, and work on that branch until you've done your changes and I'll merge them in (and the cycle continues any other time you want to make changes to the catalog plugin). |
Yes, saw changes, looks great, tomorrow I'll try to make a big catalog with lots of products and play with it a bit... Try to find bugs... |
CKEditor and CodeMirror are likely to undergo modularisation in the GS Core in the future. Currently both editors are handled with code copy-pasted from the core, but it may be best to do so separately instead.
It is relatively simply to have the catalog editor logic completely separate from the rest of the GS installation and only provide what is needed for the catalog itself. Perhaps have editor options in the Options panel?
The text was updated successfully, but these errors were encountered: