Macrura

i ran into something like this, maybe it's the html purifier? (can't test right now); after you close the dialog, if you view source, is the rel attribute still there?

@ukyo, thanks for this! Looks very cool, and I'll be psyched to test this at some point soon...

right... good solution, and good to know about the 1 skin per page...

I tried checking on some things, but as far as i can tell, the "skin" setting for each editor instance does need to be set in order to override the global skin setting. I think in the future there may need to be some additional setting for global ckeditor style to prevent the current behavior which is loading the default editor stylesheet, but then overriding the editor style with the skin parameter set in the json... So my suggestion would be to see if the module can hook into the ckeditor module with a setting for the option of global skin setting to lightwire. maybe another setting which "allow field-specific skins", and then if this is the case, then the fields that don't have a skin specifically set need to inherit the global setting, and specify that in the json (since right now there is no skin setting in the json for fields where it is not specifically set).. or maybe just modify the current system to where the skin is set in the json and no global style is loaded? but then there needs to be a way to override that.

yes - that's the one!

there is a module that allows you to add reverse (new child at top). you can also specify sort setting for children in parent template. on the frontend you can sort by any property.

yes, you have to craft your template files and you do need access to the FTP. You can use exisiting HTML/CSS templates and then integrate the calls to the Processwire API within those.

@LostKobrakai - thanks for the clarification and correction... interesting indeed.

the templates-admin is a vestigal folder from the earlier versions, but it is there in the event that the module fails, it is basically a failsafe at this point, as far as i can tell. If you are developing a new admin theme, then you would do it all self-contained in your module.

@cb2004, care to share your solution for the community?

not sure i'd use the word detriment – the whole assets management thing has been discussed a zillion times and i think most users prefer the PW way of handling assets to any alternatives. What are you trying to achieve?

hey thanks for this - works really well! Just a heads up, if you have multiple ckeditors on 1 page, you have set them all, or they will stay with the default skin

i think one workaround would be to use admin custom files (what this module grew out of), which could provide you with the ability to define your jQuery selectors manually... not totally sure - i would need to look again to see if there is some descendant selector you could use to isolate only fields you want.... or maybe use the module, but then admin custom files with custom jQuery to remove/disable it where it is messing up things?

the need you are describing was the primary motivating force behind this module: http://modules.processwire.com/modules/admin-page-field-edit-links i use it in a scenario much like what you describe (couldn't do without it!)

so maybe for single page selects, changing to a block element?

yup, just include the path to the php file in your hanna code; <?php include($config->paths->templates . "hannas/myhanna.php"); then you can include that same file form a template, or use as hanna code.

so you mean put the <i class='fa fa-edit'></i> before/outside of the anchor element?

@cloud888 welcome to the processwire forum. In order to provide the best chance of help, could you provide the following info: Processwire Version Apache, MySQL & PHP Versions List of installed modules details of any applicable/related errors in your error log (assets/logs/errors.txt) Browser you are using In addition make sure to take the following steps before reporting errors: Upgrade to the latest stable version of PW Upgrade all modules to the current version Install the diagnostics module check that your server environment meets the minimum server requirements Repair database tables address any existing warnings or failures When reporting errors that happen on a form such as the editor, please open the chrome console, or FF/firebug, and see if there are any network or JavaScript errors. Please report those errors along with your issue. Lastly Don't Panic

i had a site that was experiencing that error, once i upgraded core and all modules, i have not had any further errors;

maybe this might help? http://docs.ckeditor.com/#!/guide/dev_styles

@Manaus, if the client paid you for the site, don't they have a right to non-obfuscated php code? If you need to protect php code in templates you could look at php obfuscators, or zend guard; i once used a script that was obfuscated but the host kept quarantining it and breaking the site; they would quarantine anything with an eval and base64 code.

Some possible topics: https://processwire.com/talk/topic/2089-create-simple-forms-using-api/ https://processwire.com/talk/topic/126-anybody-did-user-registrationlogin/?hl=%2Bjquery+%2Bvalidate#entry4812 i think i learned most i needed to know about setting up api forms from these topics, but you will also need to reference the cheatsheet. try jumping in and experimenting, that's the best way to learn; once you have a form processing page, the rest is going to be mostly handled by javascript/jquery and whatever library you are using (e.g. Validate, Ajax Forms etc..) In terms of formbuilder, you can make it work with Ajax, but also consider that it can run in an iframe, which means no page reload; this works very well for the large majority of situations, at least in my experience; I would definitely give a strong recommendation to Formbuilder if you need more than 1-2 forms on your site. It is really great!

Hi nystrategi and welcome to the PW forum!! Yes, it's completely possible, and not a problem at all; PW fully supports ajax, and any number of methods for creating forms, and processing them any way you need. You can create a form processing template and have it return your ajax validation messages, or use a php file in the root that bootstraps PW and then returns the ajax messages, success or validation etc. Search the forums/docs for ajax, as well as forms; later if i have a chance i will post some links to the most relevant form topics.

gzip works 100% on all of my PW sites. So i can only conclude it is your hosting provider.

Have you read the relevant documentation on that error, here? https://processwire.com/docs/tutorials/troubleshooting-guide/page2 or google? http://lmgtfy.com/?q=processwire+%22This+request+was+aborted+because+it+appears+to+be+forged.%22