Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    porshajackson
    @porshajackson
    @JVankat
    Also is there a way for the crawler to not index our "breadcrumbs"... "ADPH Home" appears in our search results
    porshajackson
    @porshajackson
    We are also experiencing where the title in the search results is shown through the search suggestions. I am thinking this has to do with the search results utilizing header elements while our website also uses header element. Please see example here (https://www.alabamapublichealth.gov/staging/redesign/search/index.html?ss360Query=alphtn). Is there a way to possibly make the header(title) element an h4 element?
    Olesya
    @lesyaelf_gitlab
    @porshajackson apologies for the delay here - I believe my colleagues have been following up with you via email
    Marten Quadland
    @quadland_gitlab
    How can you enable suggestions in the layover popup? They only appear to work in Fullscreen mode, not layover.
    Marten Quadland
    @quadland_gitlab
    In addition to my question regarding activating suggestions in the layover popup, is it possible to use a full screen config by default, but change to a Layover view for a second search on the same page? I tried using subConfigs and SS360.changeConfig, set fullScreenConfig to nothing and add the setting for searchBox, the properties appear to update as expected but the searchBox.selector reference doesn't bind.
    Marten Quadland
    @quadland_gitlab
    @JVankat For reference, https://www.universalfurniture.com/fabrics. We currently use the top right nav bar icon to trigger layover via '''layoverTrigger: "#ss360-trigger,#ss360-trigger-mobile"''', but Layover doesn't allow Suggestions (fyi, I also noticed that suggestions do not work in the Search Designer tool with Layover and Suggestions active as well). The 2nd search area on the page, #FabricSearch, needs to use the layover, but filter the search and suggestions for layover. That currently works as expected, but since I can't toggle b/t fullScreenConfig and Layover b/t the two different search fields, I'm not able to activate suggestions in both cases.
    Jaroslav Vaňkát
    @JVankat

    Hi @quadland_gitlab - sorry for the delay, got distracted and forgot to get back to you after reading the first message. Enabling suggestions in the layover isn't curently possible (I see that this would make sense with the layover trigger, but otherwise you're the first one asking about this).

    The subConfig really wouldn't be the best way to achieve this, because the layover and fullscreen cannot co-exist in a single instance. But recently we've started supporting multiple instances of the plugin. So basically you'd have a second configuration object. There are two options how to set this up - either you make the ss360Config an array of objects (each being basically a single ss360Config, you can use an alias property to name the instance - if you need to call one of the plugin's methods), or you could use an ss360Configs object which is pretty similar, but is a map of instance names to configuration objects.

    I hope this makes sense and is at least a little helpful. We don't have any docs on the multiple instances just yet, but you can check the https://docs.sitesearch360.com/embedding example in dev tools - ss360Config and ss360Configs would be the relevant configuration objects to look for.

    Maryse
    @maryseb_gitlab

    Hi @JVankat , I'm trying to prevent some archived content to show in the search results. I have them set as noindex, noarchive, nofollow, but they still show up.

    I then tried adding the following in the NoIndex Xpaths in the crawler settings:
    //p[@class='archive_notice']

    and when that didn't work, I tried with an ID insead:
    //p[@id='archive_notice']

    But the pages keep showing in the result pages. Here is are examples of such a pages:
    https://cotesaintluc.org/announcements/new-admission-method-at-parkhaven-pool/
    https://cotesaintluc.org/announcements/parkhaven-pool-and-wading-pools-june-22/ (this one seems to have been removed from the results for now)

    So I'm guessing I am misunderstanding something. Can you help? Thanks!

    Jaroslav Vaňkát
    @JVankat
    Hi @maryseb_gitlab - your setup looks correct to me, I've just updated the //p[@class='archive_notice'] XPath to //p[contains(@class, 'archive_notice')] (otherwise we'd expect the full class name to match the archive_notice string). Manually re-indexing the first link did remove it from the index, meaning the xpaths seem to be set up correctly. I've started another re-index for your site, can you please double-check the index and confirm the archived pages aren't indexed anymore?
    Maryse
    @maryseb_gitlab
    @JVankat It seems to work now, thank you. However, is there a reason why setting the page to noindex, noarchive and nofollow is not enough for the page not to be indexed? Because ideally, I wouldn't need the XPath and the search engine would respect the noindex, isn't that correct? Thanks!
    Jaroslav Vaňkát
    @JVankat
    @maryseb_gitlab - that is correct, I suppose in this case the issue is you having two <meta name="robots" content="..."> tags in the dom, and we only process the first one. https://snipboard.io/FSsTj9.jpg
    Maryse
    @maryseb_gitlab
    @JVankat, hmm, OK, thanks for pointing that out to me. I'm not sure what plugin or if the theme is adding this additional meta robots. But if I understanstand correctly, if I manage to remove it, I wouldn't need the Xpath, correct?
    Jaroslav Vaňkát
    @JVankat
    @maryseb_gitlab that's correct.
    AEKercher
    @AnneKercher
    hello. I am trying to integrate site search 360 into our kentico site. I want to include data points via the API content that is not included in the page HTML (page type, etc.). When I go to setup data points via the dashboard, it is requiring me to add either an xpath or url pattern to the datapoint. How do I setup a data point that may not be accessible via the page html?
    Jaroslav Vaňkát
    @JVankat
    Hi @AnneKercher - your data points don't have to be set up in the control panel when indexing content via the API, meaning you can simply send the array of data points in the post body and everything should work as expected.
    AEKercher
    @AnneKercher
    @JVankat Thanks. You don't happen to know of a generic SS360 .NET client that is available for download? I see there are plugins for WP, etc., but nothing generic I could use for our custom CMS implentation
    Jaroslav Vaňkát
    @JVankat
    @AnneKercher no, we currently don't have any generic clients - only a few plugins.
    James
    @jmshey90

    @JVankat our index hasn't updated since the 12th July, and I can't seem to individually index a URL such as https://www.eastriding.gov.uk/environment/

    Any ideas?

    Jaroslav Vaňkát
    @JVankat
    @jmshey90 I'm looking into it, will get back to you in a few minutes.
    James
    @jmshey90
    Thank you :)
    Jaroslav Vaňkát
    @JVankat
    @jmshey90 the crawler seems to be stuck on the server you've been assigned to, I've switched your project to a different one and started a full re-index (seems to be running fine). Will double-check what exactly was the issue later today.
    James
    @jmshey90
    Thanks :smile:
    Jaroslav Vaňkát
    @JVankat
    @jmshey90 so I did take a look, and actually not sure what went wrong, the only reason for this seems to be your server blocking (or rather ignoring) our server (usually due to too many requests). But I'm not 100% sure about this, are you aware of some component that might be causing this on your side?
    AEKercher
    @AnneKercher
    Hello. I am trying to implement indexing using the rest API. In order to "re-index" certain content Groups, we need to delete all indexes in that group and then index them again. I am trying to use your Search api call to grab all the urls in a certain content group and then loop through and use the Delete call to delete them all. However, the Search Get call does not seem to work without a value for the "query" key (it returns 0 results if I leave it blank or query="". Is there a way to search using the api and return all indexed pages in a content group without a specific search query?
    Jaroslav Vaňkát
    @JVankat
    Hi @AnneKercher - you could use the * query to make a "all results" search, but maybe in your use-case querying the /sites/indexedContent endpoint would make more sense? See our api docs on this https://docs.sitesearch360.com/api
    2 replies
    mkcrandall
    @mkcrandall:matrix.org
    [m]
    Question: I'm injecting the script to call the search box using a javascript we use on our site to inject our navigation. This seems to create a search box just fine, but it com,es in without any classes. When I call the search box from a script in the HTML it shows up with classes. For example, the first element in the search box is '<section>'. When I call it from a script in the HTML it comes in as "<section role="search" data-ss360="true" class="ss360-flex ss360-n-section ss360-custom-search ss360-custom-search--no-margin">". When I call the search box from the javascript that injects HTML into the page, it loads as "<section role="search" data-ss360="true">" No classes. So all my CSS for the search box breaks. Does anyone know a work around for this or can suggest what I'm doing wrong? I need to be able to load the script to call the search box from the injected javascript code so it can be pushed out to all the pages on my website that use that code to build thier page. Otherwise I'd have to manually insert the code across hundreds and hundreds of pages.
    1 reply
    mkcrandall
    @mkcrandall:matrix.org
    [m]
    Actually, I think I already solved it. It looks like the code I injected from my javascript was stripped of any classes and since it was using that for the build, it wasn't showing up in the page.
    Jaroslav Vaňkát
    @JVankat
    @mkcrandall:matrix.org perfect, just let me know if you have any other issues.
    mkcrandall
    @mkcrandall
    Well, now that you mention it, I may have spoken too soon. :)
    I seem to have solved the styling issue, but now I have an issue with submitting the search term. Neither ENTER nor the input button submits any query, or at least I don't get a results screen afterwards.
    Jaroslav Vaňkát
    @JVankat
    @mkcrandall - do you have a sample page where I could check this?
    mkcrandall
    @mkcrandall
    I do, but it's behind a login that I'd prefer to not post on an open forum.
    Jaroslav Vaňkát
    @JVankat
    @mkcrandall sure, if you can provide us an access, you can just invite us with mail@sitesearch360.com and I will try to check it asap.
    mkcrandall
    @mkcrandall
    Okay, I've sent it. I've got a js file (navb.js) that injects the navigation at the top of the page (so we can have a single file from which to change navigation globally on the site). You can use web tools to open the file and have a look if you'd like. The <section> tags for the search box as well as the <script> that calls it are injected into the page via that javascript file. At least that's the idea. The only time I've gotten it to work is when the <script> to call sitesearch360-v13.min.js (on your site) was actually part of the HTML of the page and not injected by the javascript on our site (navb.js)
    mkcrandall
    @mkcrandall
    Just posting to confirm you have the information you need. Did you receive the login credentials and are you able to access my test page?
    Jaroslav Vaňkát
    @JVankat
    @mkcrandall I got it, I don't really understand what's going on, but looks like the search plugin isn't being injected, let me look into it and I'll get back to you (and sorry for the delay, it's 10PM in our timezone).
    @mkcrandall okay, can you maybe try to execute the var e=document.createElement("script");e.async=!0,e.src="https://cdn.sitesearch360.com/v13/sitesearch360-v13.min.js",document.getElementsByTagName("body")[0].appendChild(e); part of the code directly in the navb.js instead of adding it as a part of the script tag inner text?
    mkcrandall
    @mkcrandall
    There's something undefined... Web developer kit says: "navb.js:155 Uncaught TypeError: Cannot read property 'appendChild' of undefined at navb.js:155"
    And Sorry, I was uncertain how late your support was available.
    Jaroslav Vaňkát
    @JVankat
    @mkcrandall got it, your navb.js is render blocking, that seems to be the issue, can you try using the following code in navb.js? https://pastebin.com/6LJMBFPq
    @mkcrandall no problem, just saying that it might take slightly longer for me to get back to you :)
    mkcrandall
    @mkcrandall
    I pasted the code you provided onto the end of the navb.js file (and removed the line that injected the HTML <script> so as not to duplicate it). No immediate change that I've noticed. I'll try changing the elements where the script injects things.
    That didn't seem to do anything either, so I reverted it back.
    Back to the <selection><input> elemenbts it was before, that is. The javascript executing in the navb.js file I've left as you suggested.
    mkcrandall
    @mkcrandall
    I'm wondering if the order this is executed in is the problem. Since the <section> element is being injected into the HTML by the same javascript that's executing the sitesearch360-v13.min.js, can the sitesearch360-v13.min.js not find a <section> element to write to when it is executed?
    If so, what would be the difference when the sitesearch360-v13.min.js script was embedded in the page HTML? (the search function works then) But even then, the elements that sitesearch360-v13.min.js is writing to were still not being written until the navb.js file wrote them to the HTML so... I'm not sure what the difference would be.
    Jaroslav Vaňkát
    @JVankat

    Sorry, forgot to change one thing, please try the following: https://pastebin.com/TAcZsa1K

    And let me look into the rest of your questions tomorrow morning, need a fresh pair of eyes.

    mkcrandall
    @mkcrandall
    Okay. Understood. Thank you for the effort. If you want, I can un-comment the <script> tags in the HTML. The styling gets a little off then, but the search function works then if it's useful for comparison. However, that will not be an idea solution as I'm hoping not to have to manually add that script tag to multiple hundreds of web pages, which is why we have a single javascript to inject shared content across all of them.