This typically happens because 2 xtypes have the same namespace and therefore AEM tries to load both.  I've seen this with ACS Commons installed (with their multifield panel) and also a custom multifield being installed.

Not to my knowledge with the query builder.  Instead of setting the value to blank, could you set it to "none" and query for "none" instead?

1.  You're correct.  I think the point is that the content itself is located centrally and available for other authors to see, can be controlled by permissions, and you can create snippets based off of a content fragment and variations of a content fragment.  From an authoring standpoint I don't bel...

I think the difference is that you removed the value, meaning that the property name still exists on the node but has an empty string - when you save an empty value using a dialog, the property itself is removed - so the not operation looks for the property not being on the node at all.  Go ahead an...

I think the point of content fragments was to be able to create pieces of content that could potentially be used in multiples places, with or without slight variations, and house them in a single location, rather than prior where you'd need to use a reference component and have the author navigate t...

This is very vague.This is also the reason you don't implement custom multifields, because the API's are constantly changing.

You can do the following and remove the property.valueproperty.operator=notYou may also need to add @jcr:content/ to the property name, so the full thing would look like this:path=/content/myproject  type=cq:Page  property=@jcr:content/sectionEmail  property.operation=not

It's part of the Apache Configuration.  Documentation is here Versioned ClientLibs Apache ConfigurationTo configure Apache to send the right header to set a long TTL:SetEnvIf Request_URI "(\.min)?\.[a-f0-9]+\.js" long_expires=true SetEnvIf Request_URI "(\.min)?\.[a-f0-9]+\.css" long_expires=true Hea...

the most common cause of this i've found is that you're using a reserved word as a variable name or function name.  If you check the error log, you'll see the first time it errors it'll give you a pointer close to the word it failed on.

You need to update the users information in the browser.  Try the below.  It clears any current information stored in the users profile and reloads it after successful login.$(document).ready(function() { if(userName && password) { if (CQ_Analytics) { if (CQ_Analytics.ProfileDataMgr) { //Clear the c...