Broadleaf Commerce Discussion Forums

Posted: **Wed Mar 13, 2013 5:24 am**

Hi,

I am trying to incorporate "Advanced Search Module" into new BLC 2.2.0 admin.

I've received credentials and setup settings.xml as suggested. Managed to login to nexus and see those jar files.

Now following tutorial on following link:http://docs.broadleafcommerce.org/2.2/Advanced-Search.html you will notice that Tutorial mention this kind of dependency:

Code: Select all

<dependency>
    <groupId>org.broadleafcommerce</groupId>
    <artifactId>broadleaf-admin-search</artifactId>
    <version>1.0.0-SNAPSHOT</version>
    <type>jar</type>
    <scope>compile</scope>
</dependency>

while Advanced search has changed name to: broadleaf-advanced-search
Therefore, Tutorial should have updated to new status, which is:

Code: Select all

<dependency>
    <groupId>org.broadleafcommerce</groupId>
    <artifactId>broadleaf-advanced-search</artifactId>
    <version>1.0.0-SNAPSHOT</version>
    <type>jar</type>
    <scope>compile</scope>
</dependency>

Otherwise you will be getting error in maven, trying to download JAR from broadleaf nexus:

Code: Select all

[ERROR] Failed to execute goal on project admin: Could not resolve dependencies for project com.mycompany:admin:war:1.0: Could not find artifact org.broadleafcommerce:broadleaf-admin-search:jar:1.0.0-SNAPSHOT in advanced-search-releases (http://nexus.broadleafcommerce.org/nexus/content/repositories/advanced-search-module-releases) -> [Help 1]

Thank You

Posted: **Thu Mar 14, 2013 4:27 am**

Hi, one more notice to update documentation.

I've turned hibernate to validate database state while I was running application.

Documentation on link: http://docs.broadleafcommerce.org/2.2/Advanced-Search.html
states following:

Code: Select all

INSERT INTO BLC_ADMIN_SECTION (ADMIN_SECTION_ID, ADMIN_MODULE_ID, NAME, SECTION_KEY, URL, USE_DEFAULT_HANDLER) VALUES (20, 1, 'Search Facet', 'Search Facet', '/search-facet', TRUE);
INSERT INTO BLC_ADMIN_SECTION_PERMISSION_XREF (ADMIN_SECTION_ID, ADMIN_PERMISSION_ID) VALUES (20,6);
INSERT INTO BLC_ADMIN_SECTION_PERMISSION_XREF (ADMIN_SECTION_ID, ADMIN_PERMISSION_ID) VALUES (20,7);
INSERT INTO BLC_ADMIN_SECTION_PERMISSION_XREF (ADMIN_SECTION_ID, ADMIN_PERMISSION_ID) VALUES (20,8);
INSERT INTO BLC_ADMIN_SECTION_PERMISSION_XREF (ADMIN_SECTION_ID, ADMIN_PERMISSION_ID) VALUES (20,9);
INSERT INTO BLC_ADMIN_SECTION (ADMIN_SECTION_ID, ADMIN_MODULE_ID, NAME, SECTION_KEY, URL, USE_DEFAULT_HANDLER) VALUES (21, 1, 'Search Redirect', 'Search Redirect', '/search-redirect', TRUE);
INSERT INTO BLC_ADMIN_SECTION_PERMISSION_XREF (ADMIN_SECTION_ID, ADMIN_PERMISSION_ID) VALUES (21,6);
INSERT INTO BLC_ADMIN_SECTION_PERMISSION_XREF (ADMIN_SECTION_ID, ADMIN_PERMISSION_ID) VALUES (21,7);
INSERT INTO BLC_ADMIN_SECTION_PERMISSION_XREF (ADMIN_SECTION_ID, ADMIN_PERMISSION_ID) VALUES (21,8);
INSERT INTO BLC_ADMIN_SECTION_PERMISSION_XREF (ADMIN_SECTION_ID, ADMIN_PERMISSION_ID) VALUES (21,9);

But as far as I can see from BLC 2.2.0-GA, database model changed so
table "BLC_ADMIN_SECTION_PERMISSION_XREF" is not used any more. Feature of enabling some permission for some role is now in table with name: "BLC_ADMIN_SEC_PERM_XREF".

So finally SQL update script should be changed to:

Code: Select all

INSERT INTO BLC_ADMIN_SECTION (ADMIN_SECTION_ID, ADMIN_MODULE_ID, NAME, SECTION_KEY, URL, USE_DEFAULT_HANDLER) VALUES (20, 1, 'SearchFacet', 'Search Facet', '/search-facet', TRUE);
INSERT INTO BLC_ADMIN_SEC_PERM_XREF (ADMIN_SECTION_ID, ADMIN_PERMISSION_ID) VALUES (20,6);
INSERT INTO BLC_ADMIN_SEC_PERM_XREF (ADMIN_SECTION_ID, ADMIN_PERMISSION_ID) VALUES (20,7);
INSERT INTO BLC_ADMIN_SEC_PERM_XREF (ADMIN_SECTION_ID, ADMIN_PERMISSION_ID) VALUES (20,8);
INSERT INTO BLC_ADMIN_SEC_PERM_XREF (ADMIN_SECTION_ID, ADMIN_PERMISSION_ID) VALUES (20,9);
INSERT INTO BLC_ADMIN_SECTION (ADMIN_SECTION_ID, ADMIN_MODULE_ID, NAME, SECTION_KEY, URL, USE_DEFAULT_HANDLER) VALUES (21, 1, 'SearchRedirect', 'Search Redirect', '/search-redirect', TRUE);
INSERT INTO BLC_ADMIN_SEC_PERM_XREF (ADMIN_SECTION_ID, ADMIN_PERMISSION_ID) VALUES (21,6);
INSERT INTO BLC_ADMIN_SEC_PERM_XREF (ADMIN_SECTION_ID, ADMIN_PERMISSION_ID) VALUES (21,7);
INSERT INTO BLC_ADMIN_SEC_PERM_XREF (ADMIN_SECTION_ID, ADMIN_PERMISSION_ID) VALUES (21,8);
INSERT INTO BLC_ADMIN_SEC_PERM_XREF (ADMIN_SECTION_ID, ADMIN_PERMISSION_ID) VALUES (21,9);

Did I get it right?

Posted: **Thu Mar 14, 2013 9:25 am**

Yup, you've got it. I will make sure that we get these docs updated, thanks for pointing this out.

Posted: **Tue Apr 02, 2013 10:44 am**

What happened to the broadleaf-advanced-search artifact? It cannot be found in any of the repositories...

Posted: **Wed Apr 03, 2013 10:18 am**

The community version supports advanced search features via SOLR and DB driven setup.

We also have an "advanced-search" module that is part of the commercial Broadleaf offering and not publicly available.

Posted: **Sat Apr 06, 2013 3:23 pm**

Thanks for the additional information. Is there any documentation on how I get that working as explain in the link above using solr and lucene?

Thanks again!

Broadleaf Commerce Discussion Forums

Update documentation for advanced-search

Update documentation for advanced-search

Re: Update documentation for advanced-search

Re: Update documentation for advanced-search

Re: Update documentation for advanced-search

Re: Update documentation for advanced-search

Re: Update documentation for advanced-search