Forum Replies Created

  • Stefan
    Participant
    2 years, 2 months ago in reply to: Problem with query params #45442

    Sorry, the documentation and forum entries are really confusing me.
    Can you point me to some current documentation on how to style the search page and search results?
    Are all the twig templates now also deprecated?
    And what about the search-page “search-wpsolr”? That also uses a shortcode, is that also deprecated?
    /knowledgebase/how-does-the-ajax-search-work/

    If I use this code in search.php, the problem with the querystring is still not solved:

    get_search_form();
    if ( is_active_sidebar( ‘custom-widget-area’ ) ) {
    dynamic_sidebar( ‘custom-widget-area’ );
    }

    Stefan
    Participant
    2 years, 8 months ago in reply to: Real time indexing not working #38467

    Hi,

    i bought a second seat on our license so i could deactivated most plugins (except for ACF) but new posts are still not being indexed.
    I then started debugging the code, and I think the problem lies in the file wpsolr_include.inc.php, funtion add_remove_document_to_solr_index

    The problem of posts not being indexed only happens on insert, not on update or after restoring a post from trash.

    After inserting a post, the function add_remove_document_to_solr_index is first called with the $post parameter having the value $post->post_type = revision. A transient is set for the postId, but the post will not be indexed in function _add_remove_document_to_solr_index because WPSOLR_Model_Meta_Type_Abstract::get_is_model_type_can_be_indexed( $model_type->get_type() ) returns false.

    Then a second call to add_remove_document_to_solr_index is made with $post->post_type = ‘post’, but this time the post is not being indexed because the $post_id is now in $cache_indexed_posts as it was added in the first call and the function is exited at the first if statement.

    So i am pretty sure that this behaviour was introduced with version 23.5. as the code with the transients and the function _add_remove_document_to_solr_index was introduced in this version. Could you please check this?

    Stefan
    Participant
    2 years, 8 months ago in reply to: Real time indexing not working #38423

    Just to make sure: if we renew our subscription after one year, we will pay the old price?
    In that case, we would add a second seat to our subscription for dev.
    But some more questions first:
    1. Where/how do we book another seat to the subscription?
    2. Is it possible to change the url/domain after a while to use this second subscripion on? So we might use it on antoher testing server or another future live project?

    Stefan
    Participant
    2 years, 9 months ago in reply to: Real time indexing not working #38398

    Thanks,
    Is there at least discounted pricing for a second or dev-domain? It’s a bit annoying to have to buy a full licence just to be able to test/debug functionality.

    Btw: I assume that the price of 1999€ per year mentioned here is a mistake??? Might be bad for your conversion rate (-:

    Stefan
    Participant
    2 years, 9 months ago in reply to: Real time indexing not working #38360

    Happy new year to all at wpsolr!

    Unfortunately, also using cron is not solving our issue.

    In order to test with deactivating other plugins to find a cause, i want to use our dev domain (https://dev.ourdomain.com). According to this post on a dev domain no license should be asked for. But i do get the message ‘(Feature-limited version, click to activate)’.

    I am not sure if the information from the link i mentioned is still valid? What is the current situation of using a dev domain? What do i have to do to use full functionality on a dev domain?

    Stefan
    Participant
    2 years, 9 months ago in reply to: Real time indexing not working #38100

    Unfortunately, not so easily. I have only the production site available for testing at the moment. My dev site is on another domain and i don’t have a license for that domain anymore.

    I will have a look at using your cron extension for now.

    Stefan
    Participant
    2 years, 9 months ago in reply to: Real time indexing not working #38098

    Do you see it in the post header, with the classic editor?

    Not sure what you mean, but it looks like this:
    https://prnt.sc/DFZ21IarlaZq

    Stefan
    Participant
    2 years, 9 months ago in reply to: Real time indexing not working #38096

    Interesting:
    If i write a new post and publish it, i get no WPSOLR notice message. Also, nothing from this post is in my search results.

    If i trash a post, i see:
    (WPSOLR) Post removed from index
    If i then recover it from thrash and republish it, i get
    (WPSOLR) Beiträge updated in index
    And now, it appears in search results as well.

    Another thing that crossed my mind after your question about using api to publish:
    Sometimes we use a future publishing date and then the change to status publish is done by a wp cron job. Would these posts get indexed automatically?

    Stefan
    Participant
    2 years, 9 months ago in reply to: Real time indexing not working #38093

    No, all changes and new posts are made manually in the backend, we use no api for that.

    Stefan
    Participant
    2 years, 12 months ago in reply to: Theming of search results #35858

    In my template that i use inside the loop, i use get_the_excerpt() and there is no highlighting there.
    Also if i change it to get_the_content(), there is no highlighting.

    The query is set up like this:
    $search_query = ‘something’;
    $query = new WP_Query(array(
    ‘s’ => $search_query,
    ));

    Stefan
    Participant
    2 years, 12 months ago in reply to: Theming of search results #35856

    In case my question is not clearly formulated, or this is the wrong way to get to the required result:
    what i am trying to achieve, is a way to:
    1. Add a search form to a template file that uses SOLR
    2. Be able to style the results, preferably by using a WordPress template. But if it is only possible by using a twig template, that’s fine as well. An example of how to override result.twig would be appreciated.

Viewing 11 posts - 1 through 11 (of 11 total)