Try thispublic int getWidth() { Asset asset = this.getResourceResolver().getResource("imagepath").adaptTo(Asset.class); Rendition rendition = asset.getRendition("cq5dam.thumbnail.48.48.png"); try { BufferedImage bimg = ImageIO.read(rendition.getStream()); return bimg.getWidth(); } catch (Exception e...

If you're on Windows, you can modify your hosts file with these instructions [1] or OSX [2] to give you a pseudo domain.If you're talking about for an actual domain, that's a whole different subject and it wouldn't be running on your local host.[1] http://www.howtogeek.com/howto/27350/beginner-geek-...

Correct, it's a private hotfix that needs to be requested.

This is a known bug.  You can request hotfix 8879 from Adobe to address this issue.

if you only want to allow 1 path to be chosen, don't put the path field in a mutlfield.  Just have it be a pathfield.<relatedPage jcr:primaryType="cq:Widget" fieldLabel="Page Path" name="./relatedPath" xtype="pathfield"> </relatedPage>No need to over complicate.

PuzanovsP wrote... Why can't you just place robots.txt in your dam? Then you would not need additional work apart from rewrite the url RewriteRule ^/robots.txt$  /content/dam/test/robots.txt [PT] Regards, Peter  I agree with this guy.  This makes it easier to update and you can restrict permissions ...

We still see the issue with every new instance of AEM 6.1 we start.  I have a package that i took from another instance that contains the tree activation page.  If you shoot me a private message, i can forward the package over to you.

That's because OOTB the redirect functionality checks to see if the location is internal or external (see /libs/foundation/components/page/page.jsp).  If it determines it's internal (i.e. doesn't contain :/) then it appends .htmlYou could overlay the page.jsp in your page component and check to see ...

You can absolutely do that by either pointing to the asset in the DAM, or by specifying an absolute URL.  The trick from an SEO perspective is that you'll want to open it in a new window so you keep people on your site.  We typically use a link helper class where the link path/url is passed into a s...

I would re-think how you're structuring your component before you go build a custom xtype.  There is always a way to achieve the functionality you need without going down the rabbit hole that is custom xtypes (not to mention the classic UI will go away and be unsupported).What's your use case?