The image object has a getSrc() property.  You can switch your code up to utilize it:<%    Image image = new Image(resource, "image");    image.setSelector(".img");    String text = properties.get("text", "TEXT NA");%>    <%= text %><div style="background-image: url(<%=image.getSrc() %>);"></div>

Take a look at this article: http://helpx.adobe.com/experience-manager/kb/HowToUseCQ5AsMavenRepository.htmlIt basically sets up your instance of AEM as a maven repository.  I've tried it with 6 this morning and it works just fine.To find what your Maven entries are, navigate to: http://localhost:450...

I switched up my code to use the replication service instead.  I found this example on Stackoverflow.  Once implemented, all of my submissions were successfully reverse replicated.  Is there any reason i shouldn't be using this method?//pageContainer.setProperty("hideInNav", true); //pageContainer.s...

Not that are helpful.  I have an email service that triggers when a new submission comes in and i see that in certain cases these emails are being triggered but the *INFO* logs for creating an outbox item are not created, so to me that says that something is failing to trigger the reverse replicatio...

I saw this post https://forums.adobe.com/thread/1111532 and moved my save to before the reverse replicating node values were set and then obviously added another after - this didn't really help.  The next attempt i had 87 or 99 reverse replicated.

I have a custom servlet that captures a form submission and sets cq:lastModified, cq:lastModifiedBy and cq:distribute (to true).  I ran a few tests and i'm noticing that not all of the submitted content is being reverse replicated back to the author.  Out of 99 submissions, only 79 made it back to t...

I don't know why you would want to assign a segment to a page, but segments are used for targeting, so within a page you can target a component but you cannot target the page itself.  If you setup a campaign, whenever you associate a segmentation rule to that campaign when targeting content, you'll ...

I agree with edubey.  I'll however point out that the first would not require any additional code changes so you could easily add and remove events whenever you'd like, but the second you would need to do a code deployment.  Personally I would choose the first option.

Have there been any customizations to the XSS protection configuration that maybe didn't make it to the production server?

I don't have a fix for your problem, but Day Care is a good way to go.  It sounds like it's a production issue that's affecting your authors, so submit a ticket under the highest priority and work with Day Care to resolve your issue.  I've always found them to be extremely helpful.