Thinking I'll just make the fields to search through a configurable
array and then use that instead. I was really hoping that the
QueryResult object would at least have retained a reference to which
property the query was matched on. That sort of thing could be rather
useful (at least in my particular case) when programmatically handling
these results.Thanks anyways, Scott!
gjv wrote... Genius - that worked perfectly - thank you! Is there any
documentation that explains this a little better? This seems to be the
only documentation out there:
https://docs.adobe.com/docs/en/htl/overview.html You SHOULD be able to
use the ResourceResolver directly without needing to define it like
Dipti did...// just an example, "resolver" is the name of the globally
defined ResourceResolver var userId = resolver.getUserID();See full
documentation on available global objects in HTL[1]...
I'm wondering if it's possible at all to determine which property a
Query's match was found on, not just which Node?Looked around for an
answer first and only found this link[1] from kalyanar in this
thread[2].Following that, the following code will run a fulltext query
for the word "break":// make SQL query QueryManager queryManager =
workspace.getQueryManager(); // we want find 'document1' String
xpathStatement = "//element(*,mix:title)[jcr:contains(.,'break')]"; //
create query Query query = ...
Just wanted to update on something that I tried and an issue I've run
into with that method...Since my user profile property update scheduler
is a @Service, I've grabbed a @Reference to Replicator[1] and am trying
to queue up the "/home/users/a/aFb4JUP9Z7XAr1z2wQle/profile" node but
because that userId exists in the Publish instance under some other
random hash path, I'm getting the following in the publish's
error.log:2.12.2016 08:52:58.270 *ERROR* [127.0.0.1 [1482418378267] POST
/bin/receive H...
Hi all,Had a question about user profile synchronization.Existing State
(AEM 5.6.1):Right now we have an offline process create an XML dump of
users and their custom properties and store them in a file. Everyday at
5am, we've got a scheduler running in AEM that parses that file and
updates the "/profile" child node of each rep:User in AEM if a
property's value has changed. If something was changed, we mark a
cq:Page under the rep:User as modified and needing forward replication,
to which a workf...
To provide a little more detail, I'm receiving these errors on my local
AEM (6.2 with Communities FP1/FP2) servers running on OS X El Capitan
(10.11.6) with Java 1.8 Update 31 (jdk 1.8.0_31).I tested the same
functionality on some local AEM (6.2 with Communities FP1/FP2) servers
running on Windows 7 Enterprise (Service Pack 1) with Java 1.8 Update 66
(jdk 1.8.0_66), and the User Sync diagnostics tool works just fine.
Also, after going through the motions of setting up User Syncrhonization
on my local author and publisher, still can't access the diagnostics
tool.No serializer found for class
jdk.nashorn.internal.runtime.PropertyListeners and no properties
discovered to create BeanSerializer (to avoid exception, disable
SerializationFeature.FAIL_ON_EMPTY_BEANS) ) Cannot serve request to
/libs/granite/operations/content/diagnosis/tool.html/syncdiagnostics in
/libs/social/diagnostics/base/components/diagnostics/...
jayb43402168 wrote... Hi Sir, I'm sorry to hear that you are having
issues running the diagnostics. I've seen this in a specific revision of
the JDK 1.8. What JDK version are you running? Would it be possible to
upgrade it? I will add your feedback to our internal Jira for the
diagnostics for future enhancements. Thanks, again, and please let me
know what your JDK version is. Regards -Jay jdk1.8.0_31Thanks, just
wanted to let you know!
So I was looking at the documentation for User Synchronization[1],
specifically the bit about Troubleshooting - User Sync Diagnostics[2]
and when I went to pull up that diagnostics tool, I received the
following error:Infinite recursion (StackOverflowError) (through
reference chain:
jdk.nashorn.internal.objects.NativeObject$Prototype["map"]) Cannot serve
request to
/libs/granite/operations/content/diagnosis/tool.html/syncdiagnostics in
/libs/social/diagnostics/base/components/diagnostics/GET.hbs...
Just a guess here but going to say it probably changes while it's
running... If you have a look at the Built-In Lifecycle Bindings[1] for
maven plugins, it starts with "generate-resources" and then moves
through the different phases of processing, compiling, testing,
packaging, deploying, etc.Again though, just guessing here. Don't know
why you'd need to specify a specific phase instead of letting the plugin
do it's thing. [1]
https://maven.apache.org/guides/introduction/introduction-to-the-life...
Suppose I should have stated this is for more than just create(); as
this also affects getResource(); and delete();The method
getResource(ResourceResolver, String) from the type ResourceProvider is
deprecatedThe method delete(ResourceResolver, String) from the type
ModifyingResourceProvider is deprecated
Just wondering if Adobe is planning to address the deprecation of the
create(); method for the ModifyingResourceProvider
(org.apache.sling.api.resource.ModifyingResourceProvider) class that
SocialResourceProvider extends.The method create(ResourceResolver,
String, Map) from the type ModifyingResourceProvider is
deprecatedNeeding to mark my class methods with
@SuppressWarnings("deprecation") is not fun. 😞
dwalling wrote... This should be available now. Sorry for the delay Don
The JavaDoc JAR files for 1.10.60 (FP1) and 1.10.111 (FP2) are
unavailable (they're 404'ing) despite being listed in the
repository.https://repo.adobe.com/nexus/content/repositories/releases/com/adobe/cq/social/cq-socialcommunities-api/1.10.60/cq-socialcommunities-api-1.10.60-javadoc.jarhttps://repo.adobe.com/nexus/content/repositories/releases/com/adobe/cq/social/cq-socialcommunities-api/1.10.111/cq-socialcommunities-api-1....
Thanks again Calvin, that absolutely worked.Whether it was storing the
value as an InputStream instead of a byte array (byte[]) or storing the
key as "nt:file" (JcrConstants.NT_FILE), it worked. As an aside... I'm
still extremely confused on what some of the key mappings are between
Java and MongoDB. For example, "mimetype" all lowercase translates to
"content-type" through the SRP API. These pieces are extremely unclear
and not straight forward at all. 😞
calvin.wong wrote... Let me take a crack at this. In the ToDoMVC sample,
there's an example of using srp.create(), which is probably what you're
using to write to SRP. You can use the same API to create attachments.
This is roughly the pseudocode to add an attachment to a resource named
"resource". Map attachmentProps = new HashMap();attachmentProps.put("nt:file", inputStream); //
java.io.InputStreamattachmentProps.put("mimetype", mimeType); //
StringattachmentProps.put(SocialUtils.PN_PARENTID,
...
Thank you sooooo much for sticking with me on this one, Calvin! You're
incredible.Got it working with the following code:final UgcFilter filter
= new UgcFilter(); // ... required filters ... final ConstraintGroup
optionalGroup = new ConstraintGroup(Operator.And); // ... other optional
filters ... // Title "Contains" Filter final String titleFilterParam =
request.getParameter("title"); if
(StringUtils.isNotEmpty(titleFilterParam)) {
optionalGroup.addConstraint(new FullTextConstraint("*" +
titleFi...
calvin.wong wrote... Can you use FullTextConstraint and give it a try?
If you're searching for jcr:title or jcr:description, can you also try
it in the search component
http://host:port/content/community-components/en/search.html? In the
Solr admin panel, on the "query" page under the specific collection,
what would the fulltext search filter look like? I'm seeing that the
FullTextConstraint is logging without escaping the wildcards now, which
is great, but it's still not returning anything...Th...
calvin.wong wrote... The wildcard search in Solr is a known bug and it
has been fixed. The fix is in AEM-6.2-COMMUNITIES-FEATURE-PACK-2, which
will be uploaded to package share in the next few days. Will you be able
to use this new feature pack? The same fix is also available for AEM 6.1
in AEM-6.1-COMMUNITIES-FEATURE-PACK-6, which will be uploaded to package
share at the same time. Calvin,Did this not make it into the Communities
FP2 release[1]?Took an update, installed the code in my local, pe...
Thanks so much for this, JK!Quick question, will you also be pushing the
Communities FP2 (1.10.111) API and JavaDoc JARs to the maven repo[1]?[1]
https://repo.adobe.com/nexus/content/repositories/releases/com/adobe/cq/social/cq-socialcommunities-api/
Siddharth_Palaniswami wrote... I will also try to get you a snippet to
show how we add attachments via the SRP API. Hi Siddharth,Just wondering
if you were able to share that snippet? It's pretty crucial for a
service I'm working on right now.Thanks in advance!
Opkar Gill wrote... Hi Greg, Are you using VM's? An option may be to
keep monthly backups for n years. Once content has been deactivated
delete content. If you are required to retrieve any content, then you
would go back to the backup that was taken just after the date in
question and start the instance and view the content. You could also
take repository backups, but the problem with this is that if you were
required to keep content for say 7 years, can be a legal requirement for
Financial Serv...
Hi all,Question just came up recently about what we should be doing with
content that we've deactivated but must keep around for legal reasons
(for n years). We can't delete it and certain authors may still need to
access it (and its version history) for the aforementioned duration. At
the moment, it would appear that some authors have decided to create a
"deactivated-content" folder in certain site areas and have been moving
all of their content there. Ideally, we'd like to just delete content
...
pparkar wrote... We dont mandate a social schema for SRP database at
this point. Also, accessing SRP data directly from Mongo is not
supported by Adobe. Its not a bug to have redundant field [here: 'id']
across bson data. Hope this helps. I was only viewing SRP Data in
MongoDB directly to see what was persisted as a result of my Java code
utilizing the SRP API. While it's not a problem to have redundant fields
in bson data, in general, it IS a bug of the SRP API that it creates
this redundant fi...
pparkar wrote... Any particular reason to look at the mongo data
directly? Can I know how is this causing an issue? Because the SRP API
is new to me, attempting to implement it into our project's codebase,
and I'm a curious individual.It is not actually causing a problem right
now. I'm simply wondering why it happens? Something to do with the SRP
API's translation of property keys between Java and MongoDB, I'm
guessing. Which is something that I find extremely weird...Is there any
documentation ...
calvin.wong wrote... The wildcard search in Solr is a known bug and it
has been fixed. The fix is in AEM-6.2-COMMUNITIES-FEATURE-PACK-2, which
will be uploaded to package share in the next few days. Will you be able
to use this new feature pack? The same fix is also available for AEM 6.1
in AEM-6.1-COMMUNITIES-FEATURE-PACK-6, which will be uploaded to package
share at the same time. Yes, we'll be able to use it. Currently using
AEM 6.2 with Communities FP1 on my local. Looking forward to the rel...
Siddharth_Palaniswami wrote... Hi Greg, Am curious about the custom
component that you are implementing using SRP. Would it be possible to
share what your use case is? Most times, UGC based components can be
built as extensions to the Comment System APIs or Forum APIs instead of
building a component from scratch. This will give you various
capabilities that are available in our OOTB components without you
having to talk to SRP APIs directly (for the most part). Hi, we're
actually working on conv...
So, in the Solr Admin panel, I can do a search
like:postTitle_s:*atta*And it'll return results whose "postTitle_s"
property CONTAINS "atta" in it, like one particular post example title:
"Post with Attachments". This is what I was hoping for. However, when I
try to create that query in Java using ValueConstraint, it's
escaping the wildcard, making it not work. This is the code:final
UgcFilter filter = new UgcFilter(); // ... other required filters ...
final String titleFilterParam = request.getP...
