That's unfortunately not going to achieve what I want:"Still, I want to retain the ability to create pages at the /content/uc/news (or /cotnent/uc for that matter) level like normal. In these cases, the servlet appears to be triggering where it's not supposed to."The servlet should only trigger on t...

(edit: not sure why half of this is green)Again, sorry for not being clear in my inital post. Let me try to explain it a different wayAll I want my servlet to do is capture get requests to/libs/wcm/core/content/sites/createpagewizard.html/content/uc/news/articles/libs/wcm/core/content/sites/createpa...

Sorry, perhaps I wasn't being clear.I only want the srevet to run on those 2 paths, everything else should fall back to whatever other servlet was running on the default for the page creation wizard.I make plenty of there Get requests (inclusing creating pages under /content/geometrix...) for exampl...

I'm testing a servlet I use to wait for get requests to the createpagewizard.html at a given path that redirects the requests to another directory (it's a news system, so I want new articles to always go in the appropriate year/month path). It works for the specified paths, but on paths higher int h...

I have urls like this: "/content/uc/news/search-results.html?submitted=submitted&topics=topics:collegeBound" that are displaying as non-existant by the link checker. The search-results page does exist, and linking to that alone does just fine. I'd prefer not to have to disable to the linkchecker for...

Ok, that makes sense. I'm trying to find more documentation on the JS USE-Api, if anyone can point me in the right direction, I'd appreciate it.Ben

I have a search component built in sightly that I want to use to query on a number of parameters associated to find news articles (which are simply cq:pages) in our content repository. I know how I would do this with the Java Use-API, but want to use the javascript api in this particular case (partl...