by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Jaroslav Vaňkát
    @JVankat
    @Bongmaster407 we've fixed it in our dev environment, I hope we'll be able to deploy the changes tomorrow.
    Bong-Chu Papke
    @Bongmaster407
    Awesome! @JVankat thanks a lot. Could you please get back to me again when you've deployed to prod so we can double-check.
    Eric Palmer
    @DaddyOh
    What version of xpath does the backend use? Also does it suppot substring(‘str’, start, end) and concat(‘str’, ‘str’) for title extraction
    We are trying to build a if then else for title extraction
    Eric Palmer
    @DaddyOh
    even slightly complex xpath gives us an error
    concat(‘one’, ‘two’) does not return anything for faking a title
    Eric Palmer
    @DaddyOh
    @JVankat Can you look at my posts from yesterday. We need to extract title from two different places depending on ths site type. We are stuck.
    Bong-Chu Papke
    @Bongmaster407

    Hi @JVankat, I have another topic. I'm not able to implement some of the requirements that our client has regarding the filters. Just for your info, we're still using v12, updating to v13 is already on our roadmap, but we can't do that at the moment.
    Here are the requirements that I have problems with:

    1. Reset button for a filter: I saw there is a clear button in your example, but I don't have it in our implementation, does that come with v13?
    2. The state of a filter: The button to open/close the filter options should reflect the state, e.g. should be bolder, when a filter is active (when a filter option is selected). Is there a way to do that?
      Thanks in advance!

    P.S.: Do you have news about the fix regarding the multi select issue?

    Jaroslav Vaňkát
    @JVankat
    @DaddyOh sorry, I didn't get any notifications from Gitter for some reason, I will check your messages in a few minutes.
    @Bongmaster407
    1. Do you mean on top of each filter group? That comes with v13.
    2. The following CSS selector might be helpful: .ss360-filter__group--active .ss360-filter__button
      We'll be deploying the changes in a few hours, I guess it should be live in about 3 hours from now.
    @DaddyOh we use the XPath 1.0 specification.
    Bong-Chu Papke
    @Bongmaster407

    Cheers @JVankat! I guess the CSS selector you mentioned in 2. is not available in v12 too... so I guess updating to v13 is necessary for us, asap. Thanks a lot! I'll discuss that with the client.

    Another question, maybe you have an answer to that too, might also be that our client contacts you via e-mail in this regard. He can probably describe it better, but let's give it a try:
    The client set up one filter data source, type XPath, condition grabbing one of the breadcrumb levels (I think it was the first level which reflects the first level section). The filter did not seem to include any of the sub-pages of the sections though. We don't understand why, is there a limitation?

    Jaroslav Vaňkát
    @JVankat
    @Bongmaster407 I guess I see what you mean. Do you have a sample subpage for me?
    @JVankat regarding my second point from before: I think the CSS selector does only apply when the filter is open, but we would like to change the styling of the button, when at least one filter option is selected, no matter if the filter is open or closed, in fact especially when the filter is closed, so the user can spot easily that a filter is active.
    Jaroslav Vaňkát
    @JVankat
    @Bongmaster407 I'll look into the filter in a few minutes. And now I see what you mean, I could add a css class to mark filters with selected values next week if that's an option for you.
    Bong-Chu Papke
    @Bongmaster407
    @JVankat that would be wonderful, I think it's a beneficial feature anyway, not just for our client. However we still have to update to v13 in order to use it, right?
    Jaroslav Vaňkát
    @JVankat
    @Bongmaster407 okay, I'll create a ticket for this, should be implemented in v13 next Friday. And yes, you'd need to upgrade to v13, we're not updating v12 anymore (except of bug fixes).
    Eric Palmer
    @DaddyOh
    @JVankat Apparently you don’t support full 1.0 xpath or you limit the size of the xpath entered into title extraction. Abbie has some emails on this form me with more specifics. But concat(‘one’, ‘two’) is labeled invalid so some functions are disabled in the xpath. We need several to simulate a proper if then else in xpath 1.0
    Jaroslav Vaňkát
    @JVankat
    @DaddyOh I'll have to look into this specific case, Abbie will definitely assign this to me, and I'll try to look into it asap.
    Eric Palmer
    @DaddyOh
    @JVankat if you can’t get to it today I will put a //title into SS360 and reindex so we see what that looks like
    Let me know
    Jaroslav Vaňkát
    @JVankat
    @DaddyOh I probably won't get to it today, I will try, but not sure if I'll have time to look into it.
    Bong-Chu Papke
    @Bongmaster407
    Thanks @JVankat for your support! Have a nice (and probably longer) weekend. I talked to our client and will start updating to v13 now... I don't know if it's feasible to do it in one day, but it seems that we have to take this over to the next sprint anyway. Oh, and if you have any update on the sub-pages topic it would really be appreciated.
    Jaroslav Vaňkát
    @JVankat

    @Bongmaster407 I've just looked into it and see that the page you've sent me gets assigned the Magazine value for the Section filter: https://snipboard.io/0swS4e.jpg - is this the expected behavior?

    Otherwise upgrading to v13 shouldn't take that long, unless you have a lot of custom styles, as we've modified our class names, but we can help you with the migration.

    And yes, it's holiday on monday in Germany, thanks! Have a nice weekend.

    Eric Palmer
    @DaddyOh
    @JVankat I’m going to put //ttitle in for the extraction and reindex - When you get to this let me know if there are restrictions to xpath 1.0 that you have in the system or other limits that would keep us from doing something like: concat(substring(//h1[1], 1 div boolean(/html/head/meta[@name='ecosystem'][@content='hermes'])),substring(//title[1], 1 div not(/html/head/meta[@name='ecosystem'][@content='hermes']))) which is valid xpath 1.0. There are other ways to do this but they are longer strings of xpath code.
    Bong-Chu Papke
    @Bongmaster407

    @JVankat, well that's because our client tried to include the sub-pages by adding a few more filter data sources, I think for the second and third level breadcrumb items. Actually it shouldn't be like that. All pages under "News and media" should be included in the filter "News and Media". Let me have look...

    Argh, now I see what the problem is... the initial XPath does not return anything for the sub-pages, probably because the breadcrumb is placed somewhere else in the DOM... I didn't know that. So okay, that makes sense now. I haven't been looking into that problem before. I think the solution for that is to gather all XPaths that return the first breadcrumb item for all pages, right?

    Jaroslav Vaňkát
    @JVankat
    @DaddyOh I don't think we support this, not sure why, maybe some limitations of the library we're using, I'll take a proper look next week and will keep you posted.
    @Bongmaster407 yes, that would be a solution, or maybe there could be a more generic xpath applying to all pages? I can take a look next week.
    Bong-Chu Papke
    @Bongmaster407
    @JVankat no worries, I'll hand that over to the client.
    And yes, unfortunately we're using custom CSS which probably makes it a pain to upgrade to v13. Is there maybe a guide that you can provide me with?
    Jaroslav Vaňkát
    @JVankat
    @Bongmaster407 unfortunately there's no guide, as we've changed really almost everything, and most of our customers don't even use custom css. But I'm starting to think that it was a mistake :) You can email us the stylesheets and we'll take a look and can transform it for you - we've been counting on helping with the migration. Btw. the filter behavior should now work in the control panel and soon everywhere (still need to deploy the changes on two of our servers, but the main one is up to date).
    Bong-Chu Papke
    @Bongmaster407
    @JVankat Wow, thank you very much! I just checked it in the control panel, it's marvellous. I'll ask the client to test it on Monday, they will really be happy :)
    Don't worry regarding our migration to v13 for now. I'll start and if I get stuck I get back to you. Thanks for the offer.
    LesKent
    @LesKent
    Hi there. I'm having a problem where some images don't show up in the search results but the suggestion results do have an image. When I look at the generated HTML from the search results the ones without a picture have a correct image URL but have style='display: none;'. Is this somehow related to small images?
    Jaroslav Vaňkát
    @JVankat
    Hi @LesKent - can you send me a sample query and your siteId? Then I'll take a look. This might be due to the aspect ratio of the image.
    LesKent
    @LesKent
    If you go to https://www.progent.com and enter "sonicwall" in a search for example you will see the first two results don't have pictures displayed but do have a link to an image. Our siteID is www.progent.com
    Jaroslav Vaňkát
    @JVankat
    @LesKent thanks for the details, this is indeed due to the large aspect ratio of some images - we decided to hide those, because those are usually irrelevant images. When I'll get to the office (it's just past midnight in our timezone), I will add a configuration option so you'd be able to disable this behavior.
    LesKent
    @LesKent
    @JVankat thanks for looking into this. It seems like the behavior should be if the primary image is not available or acceptable because of size or ratio then it should use the default image instead, which is not how it works now. What is the purpose of having multiple image XPaths? Does it not always use the first image it finds?
    Jaroslav Vaňkát
    @JVankat
    @LesKent this is on the client side. Multiple XPaths could be useful if you need to pick different images from different page types, but if multiple images match the xpaths, then we only pick the first one. I'll ping you in about 3 hours - once the setting is available.
    Jaroslav Vaňkát
    @JVankat
    @LesKent you can now set the ss360Config.results.checkImageQuality setting to false. Just let me know if you need any help with this.
    Bong-Chu Papke
    @Bongmaster407

    Hello, I hope you had wonderful bank holiday yesterday! At least the weather was marvellous. And I managed to update our ss360 integration to v13, yay!
    But, I have another issue now. When I submit a search term, open the filter (we only have one) and select at least one filter option, the markup of the result heading with count (#ss360-search-result-heading) changes and the caption (ss360Config.results.caption) disappears. Could you please take a look into it.

    initially before filtering:

    <h2 id="ss360-search-result-heading" class="ss360-layer__heading">
      <a class="ss360-layer__heading-anchor" tabindex="-1" href="#">
        <span class="ss360-count">211</span> results found
      </a>
    </h2>

    after filtering:

    <h2 id="ss360-search-result-heading" class="ss360-layer__heading">
      <span class="ss360-count">216</span>
    </h2>
    Jaroslav Vaňkát
    @JVankat
    Hey @Bongmaster407 glad you managed to upgrade! I could reproduce the issue, will try to fix that asap.
    Bong-Chu Papke
    @Bongmaster407
    Hi @JVankat, thanks a lot!
    Jaroslav Vaňkát
    @JVankat
    @Bongmaster407 should be fixed now (v13.1.113).
    Bong-Chu Papke
    @Bongmaster407
    Thanks a lot! @JVankat
    Bong-Chu Papke
    @Bongmaster407
    @JVankat another question. What is the button for?
    <button class="ss360-skip-link ss360-skip-link--group ss360-n-button">Skip Filter Group</button>
    Jaroslav Vaňkát
    @JVankat
    @Bongmaster407 this is mainly to make keyboard navigation easier, e.g. if you want to navigate using the tab key, you can skip a whole group without having to tab through all the multiselect options.
    Jaroslav Vaňkát
    @JVankat
    @Bongmaster407 the filter groups with selected options now (v13.1.116) have the ss360-filter__group--selected class name.
    Bong-Chu Papke
    @Bongmaster407
    Oh, wow... really? That's fantastic! @JVankat thank you very much! We can do wonderful stuff now :)
    Bong-Chu Papke
    @Bongmaster407
    Thanks a lot @JVankat and the whole team from Site Search 360°! Tomorrow we will review the search filters with our client. You contributed a lot to the successful implementation of the filters for Zurich.com in the last few days. Thanks a lot for this!
    Bong-Chu Papke
    @Bongmaster407
    And also a big thank-you from our client!