Are loading any custom ExtJS libraries in your page properties. That's generally the cause of this problem. If you have custom ExtJS widgets that you reference in your page properties you need put the those JS libraries in a seperate clientlib folder and set the category for that client lib to be cq...

One option would be to use /etc/map to do an internal Sling redirect from .aspx to .html, but I am not sure how that would play with the vanity URL. You'd have to test that out and see if you needed the vanity URL to be .aspx or .html after the internal redirect. Also to make sure that one wouldn't ...

It isn't any different than the sling:resourceSuperType - if you want utilize the parbase you declare it as your component's sling:resourceSuperType. There is nothing special about the parbase - it's just component that happens to serve a special purpose in you component hierarchy. I'd say 90% of co...

The primary purpose of the parbase is to provide a location for common selector based scripts that are shared by multiple components. If you look at the scripts contained in /libs/foundation/components/parbase you will see the image script (which happens to be a servlet) and the scaffolding scripts....

What is your max Heap size set to? 

There are several possible reasons that I can think of:Referrer filter configuration (see for details on how to configure https://dev.day.com/docs/en/cq/current/deploying/security_checklist.html#Issues with Cross-Site Request Forgery)Dispatcher filters (by default dispatcher filters out post actions...

Try looking at the Trusted Header Authentication handler which is intended for SSO integration. I believe it meets you use case -  http://dev.day.com/docs/en/cq/current/deploying/single_sign_on.html#Configuring Trusted Header Authentication and SSO. 

I think you are going to have to give us a little more information than what you have provided. The first question is did you check error.log to see if there were any exceptions when you try to view the page? One guess is that you getting a compile error because log is probably already defined. If y...

There several ways in which a page can be published. In addition to the user simply activating the page from say the side kick or the Sites console a page can be published through a workflow (either by the author starting a workflow directly, or via the Activate Later function. In the case of activa...

If the number of variations is small the most common way would be to use a selector (/content/site/en/page2.option1.html or /content/site/en/page2.option2.html). Selectors are cachable and probably the best solution for what you have described. You just need to make sure you whitelist your selector ...