Where to replace example schema? - search

I am using TYPO3 7x and want to use SOLR search. I created a core using SOLR Admin UI but getting an error of "unsupported schema". please see screenshots.. I am totally new to SOLR and TYPO3, please help.. Screenshot of Error,
Screenshot of core in SOLR Admin

The Solr layout is usually a home that contains solr.xml file and under that one or more collection/core directories, each containing core.properties file.
In your Solr screenshot, instanceDir is that collection/core location and it is /var/solr/data/core_en. The schema.xml and solrconfig.xml then live under the conf directory within that.
Notice that schema.xml would most likely be renamed managed-schema on the first run (at least with default solrconfig.xml). When you are copying your configs over, make sure to remove old managed-schema as well.
Now, one complication is that your Typo3 seems to be looking for it under /solr/core_en, which is not the same path as /var/solr/data/core_en. I would double check what you have in /solr/core_en as well, perhaps you have two conflicting installation or similar.
After you replace the configs, restart Solr or - at least - reload the core in Admin UI's core screen.

Thanx for your reply. There was no problem with the paths. When i was making the core, I moved conf folder from /typo3conf/ext/solr/Resources/Private/Solr/configsets/ext_solr_6_1_0 to /var/solr/data/core_en but forgot to move typo3lib folder. It worked now. but search is still not working. Whenever i search somthing it says "Nothing found for "here is the term I search". " . In the next step when i index in search module, It gives me "Manual Indexing
An error occurred while indexing manual from the backend". screenshot 1, and when I click show error it gives this.
I'm taking help from docs.typo3.org/typo3cms/extensions/solr/Backend/ConnectionManager.html
I appreciate your help.

Related

TYPO3 v. 11.5.21 Search field is not working properly

as expected, there coming more and more with TYPO3. I'm very in TYPO3 and working with the bootstrap package. Therefore I don't understand loads of stuff.
The task is actually very simple (i guess). I just want to include a search field on in my page with indexed search. I included the extension with the extension manager.
So far so good, the search field is shown and it's able to find content on my page, but when I select one of the search results this page is shown:
Error message
Does anyone understand what happened here?
Many thanks in advance for your hints!
cheers,
expikx

SharePoint: Search box not using search settings

I'm having a problem that just randomly occured, and I have no idea what caused this and how to fix it.
So I have a searchbox that is supposed to use my search settings. Here are my current search settings:
Settings
Settings 2
My problem is that even though I configure my searchbox to use this sites' search settings, it ignores it. Instead of using /results.aspx?u={searchboxQuery} as specified in the settings, it uses /results.aspx?k={searchboxQuery}
I'm also using a custom Result Source:
{searchboxQuery} Path:https://mypage/Pages
The searchbox works if you provide exact matches, but if you try to shorten a word, no result is displayed. The result query itself works correctly, displaying all the correct pages, but not with search queries.
Any help would be highly appreciated, it's quite an annoying problem
I remember running into this a while back. I ended up using a Search Results template from the Pages library (Publishing needs to be turned on. Trying to create the connections myself was too much of a headache.

PHPMaker created pages give 403 error

I created an admin section for a website of mine using PHPMaker - as I usually do. The website is made from scratch, no wordpress or anything else involved.
In some apparently "innocent" tables, if I try to edit them, I get a 403 error. It never happened, and I used PHP maker for at least 15 websites of mine, so I am puzzled.
It happens only on 2 tables out of 15, and as said, they are fairly innocent. Nothing fancy compared to the other ones.
This is what I've tried:
there was no .htaccess file in the admin directory, so I also tried to insert an empty one
clearing the cache
visiting the page in private mode
all file/directory permissions are ok
regenerating the project and uploading it again, to a different directory
What else can/should I check?
There is a .htaccess file on the root directory of the server to handle some "pretty url", but it should not matter since the admin section is under a specific directory. Or should it matter?
Thank you
At least, I found the problem: every time I was trying to insert an iframe or a script, somewhere somehow somebody (...) was parsing it and it was blocking it for - I guess - security issues, so I let the user to insert the script without the <script> tags, added later in PHP simply with:
print "<script>$readFromDB</script>";
In each insert action, PHPMaker will parse the word
<script
and converted to
<s<x>cript
You have either get the inserted rowid and update the value again OR each time you have to remove the '< x >' to view the value correctly.
Take a look at my answer here: PHPMaker issue

coldfusion 10 moving to solr from verity

We are moving from coldfusion 9 verity to coldfusion 10 solr in an application that searches PDF files that have metadata attached to them. We get very different results in testing. We eventually found that solr is searching the file contents very differently than verity. Is there something we can "tweak" to make solr searching more efficient or get them to search the same? We sometimes get very different results searching on a single word, not just multiple words.
Edit: I found that the PDFs I was using were mostly really old and after doing a batch save in Acrobat to resave them as another version, I got much better results. That and the default operator in Verity was AND and SOLR is OR, so I changed that in the jetty config file under my collection's folder. This all helped, but other than that, I'm getting little differences here and there. I hope this helps or helps anybody else that sees this post. Not sure what else I can do to really "tune" it.

MX Google maps throws a "failed to open dir" php error

I have MX Google Maps installed on an ExpressionEngine website.
When editing a field ( any field ) I'm greeted by this error:
A PHP Error was encountered
Severity: Warning
Message:
opendir(/opt/www/old_site/themes/third_party/mx_google_map/maps-icons/):
failed to open dir: No such file or directory
Filename: mx_google_map/ft.mx_google_map.php
Line Number: 212
MX google maps tries to use the theme folder path specified in an old site.
I've used the correct theme folder path in my general configuration and global template preferences, but MX google maps seems to stick to the old path.
Do I have to change it somewhere else, what am I doing wrong ?
I think I've had this problem before, and I'm pretty sure Max Lazar saves the path in the database for some reason. Do a search for www/old_site/ on your DB and see if you get any results.
Cheers,
Rob
Looking at the add-on source code, it appears to be checking a setting path_markers_icons, and if that is blank, defaulting to the EE theme path.
You should be able to find the path_markers_icons setting under the global fieldtype settings (under Add-ons > Fieldtypes). I suggest you make the setting blank so that it uses the built in EE theme path and doesn't trip you up in future.
Also, going by your line number it looks like you're not running the latest version (or at least the version that I just downloaded), so I suggest you upgrade.
Shot in the dark here: did you have a look in the exp_site table and in the site_system_preferences field? To echo Rob's thoughts, I vaguely remember having problems with that one on an MSM site, albeit not with that add-on. It's base 64 encoded so use this to decode.
http://www.opinionatedgeek.com/dotnet/tools/base64decode/
If your "old" theme_folder_path value in there, change it and base 64encode it to see if it changes something. Although, specifying theme_folder_path and theme_folder_url in config.php should override whatever is in the DB.

Resources