By default, ASPMAKER 11 (and higher) come with the basic CKEDITOR toolbar.
If you wish the full capabilities of CKEDITOR:
1) deploy out your normal ASPMAKER project folder to the web server
2) go to http://ckeditor.com/addons/plugins/all and use the “CKBUILDER” on the right side to build out your custom build of CKEDITOR (I just took “everything”).
3) save the file
4) extract, and overwrite your existing CKEDITOR file inside the ASPMAKER folder on your server.
5) edit the CONFIG.JS file and add this line config.allowedContent = true;
that will make sure you can save HTML without certain tags getting stripped out.
Very easy fix.
Edit the config.js file (inside the CKEDITOR directory)
config.allowedContent = true;
before the close bracket tag.
save the change.
Edit the ewcfg11.asp (or slightly different filename depending on your version of ASPMAKER)
set this line to FALSE:
Const EW_REMOVE_XSS = False ‘ True to Remove XSS / False to skip
quit the open web browser (all open instances of that browser).
launch the browser.
retry pasting IFRAME code into SOURCE on CKEDITOR. Should work now.
If you are using ASPMAKER by HKVSTORE to build web admin interfaces, and you’ve arrived at this page, it’s likely because the Image Resizer ASP.NET add-on is not working for you.
Does this look familiar to you?
Warning: ASP.NET 2.0 or later is required but ASP.NET script is not executed properly on this server:
see this screenshot:Here is the solution to the issue.
- You need to have a HOSTS file entry on the server that will allow the server to resolve the domain name for the website you are using ASPMAKER and the Image Resizer on. This is because the ASP.NET resizer uses MSXML2.ServerXMLHTTP to locally fetch and resize the image. If there is no HOSTS file entry on the local server, there is no way for the resizer to work.
- Open the HOSTS file and add an entry like this
- X.X.X.X your.domain.name
- Make sure the upload folder is set properly in ASPMAKER here:
- This path will be relative to the folder you have deployed the ASPMAKER files to on the server. For example, if the ASPMAKER files are in the directory /123/ then the upload folder (pictured above) will be /123/upload-temp/
- set the permissions properly on the /upload-temp/ folder. this means adding machinename\IUSR and granting full control.
- Inside ASPMAKER, make sure the destination folder is correct. Note I had to use “../” to get ASPMAKER to upload to the correct path off the root. It is NOT necessary to grant this folder any special permissions.
- Make sure the base site itself has a valid application pool assigned. Here’s what mine looks like (It is not necessary to have an application for the subdirectory where the ASPMAKER app).
- NOTE: depending on your setup, it may be necessary to set the .NET CLR version to v.2.X above. (I HAD TO USE v.2.X for my setup…)
- Adjust the maximum file upload size in ASP. ASP->Limits Properties ->Maximum Requesting Entity Body Limit. The default value is 200,000 (200000) which is 200,000 bytes. I upped mine to 20,000,000 (leave out the commas here).
- Launch the ASPMAKER web admin and try uploading an image. The above should take care of all the issues.
Let me know if this saves you a headache!