yezzz

I’m using the file from wpsolr_5.xx.zip from https://wpsolr.com/?wpdmdl=2071

solrconfig.xml, june 3rd 2016, CRC 69C67C9C
schema.xml, march 16th 2015, CRC AFD6E3F3

Is there a more recent version?

Yes, that line you mention is readable, line 155.

Please advice.

Well, I followed your server setup instructions and using your xml files.

Are you talking about dynamic schema APIs (as commented on line 132-153 of solrconfig.xml) ?

I thought that I had given you a very verbose description of all problems…

WPsolr output on the front end is not working.

* Warning: strtotime() expects parameter 1 to be string for each results. The date then renders as

01/01/1970

* Title>a and author showing “Array” instead of the actual strings.

* autosuggest does not work

Ok, that looks the same as what I did, except that I placed the xml files too late (after doing it later I did remove/reindex from wpsolr “send your data”).

Anyway, I set up an index following your procedure, changed wpsolr settings to new path, then in “send your data” it showed:

A total of 0 documents are currently in your index “mytest”
0 document(s) remain to be indexed

Resaving a post set the latter value to 1, and I was able to index 1 post only. Enabled “Stop real-time indexing” to see if that would trigger anything but no go. Then ended up emptying the index, then could normally index everything.

For retesting I removed the wpsolr configuration, and the solr index and folder. Then did the setup again and this time all went well.

But the bugs above remain. I should add that the autosuggest spinner (loading_sugg class) is not removed after aborting the search ie. clearing the input and blurring it.

One more I found: with realtime indexing enabled, after changing a post the “send data” shows

1 document(s) remain to be indexed

Maybe a bug with updating that number, as I first verified with a solr query that the index was already updated.

I disabled all other plugins and tried various themes. PHP version 5.4.7. I read the info about the spellcheck but I assume modifying the xml file relates to v4.0. I’m using the v5.0 file ( solrconfig.xml CRC: 69C67C9C).

Not sure if it’s elevant, but this is a multisite install. Running the code on the main domain.

Here’s an example output I from a query in solr admin:

{
  "responseHeader": {
    "status": 0,
    "QTime": 0,
    "params": {
      "q": "*:*",
      "indent": "true",
      "wt": "json",
      "_": "1467225329769"
    }
  },
  "response": {
    "numFound": 58,
    "start": 0,
    "docs": [
      {
        "id": "417",
        "PID": [
          417
        ],
        "title": [
          "Example title"
        ],
        "content": [
          " Content text.... "
        ],
        "author": [
          "reisfavoriet"
        ],
        "author_s": "https://reisfavoriet.loc/author/reisfavoriet/",
        "type": [
          "post"
        ],
        "date": [
          "2012-09-18T00:30:34Z"
        ],
        "modified": [
          "2012-09-18T00:30:34Z"
        ],
        "displaydate": [
          "2012-09-18T02:30:34Z"
        ],
        "displaymodified": [
          "2012-09-18T02:30:34Z"
        ],
        "permalink": [
          "https://reisfavoriet.loc/bijzondere-gebouwen/example-title/"
        ],
        "numcomments": [
          0
        ],
        "categories_str": [
          "Bijzondere gebouwen"
        ],
        "flat_hierarchy_categories_str": [
          "Bijzondere gebouwen"
        ],
        "non_flat_hierarchy_categories_str": [
          "Bijzondere gebouwen"
        ],
        "categories": [
          "Bijzondere gebouwen"
        ],
        "_version_": 1538416134787694600
      },

Hope this info helps.

Also

wpsolr successor

is interesting. Any info on that? Hope it also works with self-hosted index. Premium features will be fine.

Thanks for your reply. Forget to report another issue: it screws up my gantry theme like I reported HERE. Seems to only happen if I get Solr HTTP error: HTTP request failed, couldn't connect to host (because I forgot to start the server ?? The page body then starts with > character and the css is not loaded.

Yes. Try to see what happens with the ajax in your console.

Spinner shows and a see an ajax request which after about 10 seconds returns:

{"message":"Solr HTTP error: OK (404)\n<html>\n<head>\n<meta http-equiv="Content-Type
" content="text\/html; charset=UTF-8"\/>\n<title>Error 404 Not Found<\/title
>\n<\/head>\n<body><h2>HTTP ERROR 404<\/h2>\n<p>Problem accessing \
/solr\/mytest\/suggest. Reason:\n<pre>    Not Found<\/pre><\/p><hr><i&gt
;<small>Powered by Jetty:\/\/<\/small><\/i><hr\/>\n\n<\/body>\n<\/html
>\n"}

It can’t connect, but after I click the search button I do get search results.

Will be done in the successor of wpsolr.

Great, on top of hardcoding the page, the page check is a waste of resources and may even slow things down. Have a look at the wp-greet. With that plugin you put its shortcode on page(s), then in the admin this will get detected and you select the page you want to use.

Also, custom templating would be great, and it may be useful to have multiple search engines, each with its own solr index and set of wpsolr settings. Eg. have 1 for general site search and another for, say, products in the shop. Have a look at settings set of link library. It’s an amazing plugin.

What fields ? and where are you seing them ?

I get a title like this:

<div class="p_title">
<a href="https://example.loc/slug/">Array</a>
</div>

Maybe I didn’t properly complete the setup. Here’s what I did.

1. Installed solr 5.5.0 on local server in opt folder, then started solr with c:\xampp\opt\solr\bin\solr start

2. in https://localhost:8983/solr saw I needed to create a core, so created a core/instance. Dir is c:\xampp\opt\solr\server\solr\mytest

3. Didn’t know where to put those xml config files, and also saw them in a plugin folder, so I didn’t do anything with them (later placed them in mytest/conf folder).

4. setup wpsolr to use this path: /solr/mytest

Then after completing setup I started indexing the documents which seems to work fine.

BTW, running on a windows7 machine. Xampp version… errr very old (control panel v3.1.0 beta6)

Yeah, or could it be wpautop wrapping stuff in p tags?

If it’s actually br tags then a quick patch would be to style them to not break ??

Hmmm weird… did you try creating another category after that?

To have an “all links” category you’d have to do that manually as far as I know. I’m actually adding all my links to such a category and using that with “default category to be shown” and “show one category at a time”.

The reason is that search results show links multiple times if that link is in multiple categories, but I noticed it does obey the above settings with the specified cat id. It then acts as a filter, preventing duplicate results.

Note that I haven’t looked at new features and not updated the plugin for a while though, so maybe things have changed.

As for other features you ‘ll have to wait for a next major version which I hear is gonna use it’s own content type or taxonomy which will have more possibilities. I asked for boolean logic (eg show links that are in cat X AND cat y) or even faceted filtering (show links based on eg. various custom field values).

1. You can set this in the links tab/section on the library settings tab.

2. Use the link date format in the general options. Simply remove the characters that represent the time, eg. g:i a

Are you using ajax switching to display the links? Then you may want to check for errors in your console (press F12 in your desktop browser to open dev tools).

You did place the [ link-library ] shortcode to show your links, right?

I’m curious about this. Did you completely remove the before and after html elements of the fields you’re using? Can you post a link to your page?

Ah ok, so it was a misplacement issue due to theme incompatibility.

The plugin uses FB comments plugin, which inserts content in an iframe (source: https://www.facebook.com/plugins/comments.php with a bunch of parameters). This means that the content really isn’t even in the page at all… even in the free version.

If you talk about placement: by default it puts the iframe in the comments section of the page. Only when you use the shortcode it will be placed where you put the shortcode.

As for the pro option: you can see the “top” option in the free version, just before the pro popup appears, so you knew what extra’s you would get when buying pro.

Soo, I’m really having trouble understanding your point. Btw, I’m not a plugin author, nor am I affiliated with them.

I recently switched from another plugin and did not lose the comments. They’re attached to the page via the url.

https://developers.facebook.com/docs/plugins/comments

Lol… yeah I recognize the “blindness”… something with trees and forest ??

But did you not encounter the bug when you tested it? Also, anything on the rendering/output issue with my wrapper?

And thanks for the email re tinymce. I’ll do some testing with that.