I'm trying to follow along the haystack tutorial. I run into an error when I run manage.py rebuild index
I get the following error:
WARNING: This will irreparably remove EVERYTHING from your search index.
Your choices after this are to restore from backups or rebuild via the `rebuild_index` command.
Are you sure you wish to continue? [y/N] y
Removing all documents from your index because you said so.
All documents removed.
/Users/heri0n/python_env/lib/python2.7/site-packages/django/db/models/fields/__init__.py:808: RuntimeWarning: DateTimeField received a naive datetime (2013-04-07 16:14:15.481145) while time zone support is active.
RuntimeWarning)
Indexing 1 notes.
Failed to add documents to Solr: [Reason: None]
<response><lst name="responseHeader"><int name="status">400</int><int name="QTime">6</int></lst><lst name="error"><str name="msg">ERROR: [doc=haystacktester.note.3] unknown field 'django_id'</str><int name="code">400</int></lst></response>
I did run manage.py build_solr_schema > ~/solr-4.2.1/example/solr/conf/schema.xml
I had to create the conf directory manually as it did not exist. I noticed the tutorial uses Solr 3 while I'm on 4. Did the location of the conf dir change perhaps?
The problem is with the Solr (haystack document use v3.5.0, here you may be using the latest) not finding the configuration file. These 3 steps worked for me
Place the schema in solr-x.y.z/example/solr/collection1/conf/schema.xml
In the schema change stopwords_en.txt to lang/stopwords_en.txt
Add the version field (as mentioned below) to the schema in the fields section
<field name="_version_" type="long" indexed="true" stored="true" multiValued="false"/>
For more information check out the same discussion in GitHub
This is more of a comment, but due to my lack of points I am unable to comment...
Has anyone figure out a soltuion to this? I'm having the exact same problem. The field is being created in schema.xml as such:
<field name="django_id" type="string" indexed="true" stored="true" multiValued="false"/>
I have restarted Solr (multiple times), and I am 100% positive my schema.xml code is correct. What the heck is going on here?
EDIT: I switched to Elasticsearch and have no problems. However, I'm sure others out there would find help to this question useful.
I had to clone the haystack source code and do some hacks as follows :
In the /haystack/management/commands/build_solr_schema.py , I commented DJANGO_ID in the build_context() func.
Then in /haystack/templates/search_configuration/solr.xml , I replaced {{ DJANGO_ID }} with "django_id" and everything worked ok.
I think the {{DJANGO_ID}} is not being replaced with "django_id" when you generate schema.xml.
Related
I'm working with Sitecore 7.0 rev 131127 and when I tried to go to the Content Editor I'm getting the following error:
But when I try to go to other modules such as Marketing Center, it is working.
I tried the following changing following value to false on Sitecore.Social.config but it didn't work for me.
<!-- Is Profile updating at user login functionality enabled. -->
<setting name="Social.ProfileUpdating.EnableProfileUpdating" value="true" />
Can anyone advise on this ?
This is a configuration issue if I'm not mistaken namely your Lucene Index Configrations files within the App_Config/Includes folder. Most likely the Sitecore.ContentSearch.Lucene.DefaultIndexConfiguration.config file or a custom one created in your solution.
Usually you see these sorts of errors when a TypeConverter is missing from the config, as you can see its referencing the Typeconverter in the StackTrace. E.g. For the index to correctly convert DateTime this line is added to the DefaultIndexConfiguration.config file. Confirm the following line is in your *.DefaultIndexConfiguration.config file(s)
<converter handlesType="System.DateTime" typeConverter="Sitecore.ContentSearch.LuceneProvider.Converters.IndexFieldDateTimeValueConverter, Sitecore.ContentSearch.LuceneProvider" />
It's also worth identifying which Field is causing the error. Perhaps a new field has been added recently to a template or the raw value in a DateTime field is not in the correct format for a DateTime Sitecore stores its dates in ISO 8601 formatted i.e. yyyyMMddThhmmss
I ran into this issue recently - when I try to replace the Wix Product version number using NANT XMLPOKE task, it returns the following error message "No matching nodes found".
<xmlpoke file="..\Setup\abc.wxs" xpath="//Wix/Product[#Version]" value="${version.label}" >
Initially I thought that this was an issue with XPATH statement that I wrote. So I kept trying with different XPATH (like \Wix) and I kept getting the same message back.
Understood from a blog that this is happening due to the namespace definition with the WiX element. Please find below the solution, in case someone doesn't find the blog.
The issue happens because of the namespace definition within the Wix element. You have to add the below changes to get the XMLPOKE working:
<xmlpoke file="..\Setup\abc.wxs" xpath="//wx:Wix/wx:Product/#Version" value="${version.label}" >
<namespaces>
<namespace prefix="wx" uri="http://schemas.microsoft.com/wix/2006/wi" />
</namespaces>
</xmlpoke>
Reference: Soledad Pano's blog
I am trying to add a few new columns to certain tables in Joomla, since i need to migrate these fixes from dev to production i am trying to do this the clean way, updates trough the filesystem.
I have followed a few tutorials concerning this and did the following.
I created the folder updates/sql and put a new sql file in it with my new version (1.5).
I changed the version number in my xml file.
I refreshed my cache in the backend.
Here are the codes I used:
My version:
<version>1.5</version>
The update node:
<update>
<schemas>
<schemapath type="mysql">sql/updates/mysql</schemapath>
<schemapath type="sqlsrv">sql/updates/sqlsrv</schemapath>
<schemapath type="sqlazure">sql/updates/sqlazure</schemapath>
</schemas>
</update>
The sql file:
ALTER TABLE `#__mycomponent` ADD `field` VARCHAR(255);
I tested my query directly against the database and it worked, what am I missing?
Short answer - Joomla!'s DB migration tool only does them after uploading a new component via the Component Manager. It doesn't check for a migration on every $_REQUEST, which is what your question suggests.
Longer Answer
Make sure you run the upgrade via the component manager. Simply over-writing the files doesn't trigger Joomla's migration process. Check the #__schemas table for your component's ID, and it'll have a corresponding database schema version #. If that version hasn't incremented yet, then the migration wasn't applied.
Part of the problem is
I am trying to do this the clean way, updates trough the filesystem
While I agree with you, that would be the clean way: Joomla! wants you to do things the Joomla! way ;-)
Important Note about Joomla! SQL Files
SQL files cannot contain C style comments (# comment here), and must contain comments like this -- comment here Spent a few hours debugging my own code, and had to re-run an upgrade about 25 times to figure out where the database schema migration was failing.
Comments may support the /* Comment */ style syntax, but I have yet to test that as extensively. YMMV.
A long time ago I first setup a website in Umbraco. This seemed to be working fine.
I have now come back to it about a year later, and was initially getting the following error when selecting a Document Type (any document type in the Settings tab):
A bit weird, because earlier I didn't have this issue, but fine. I do what it says, and add <identity impersonate="true"/> to the <system.web> node in web.config.
While it does fix the initial issue, I now have the following on all document types:
When trying to create a new Document Type, I get the same kind of error, but then the ReturnUrl part is ReturnUrl=/umbraco/create.aspx?nodeId=init&nodeType=inittemplates&nodeName=Templates&rnd=20.2&rndo=21.2&nodeId=init&nodeType=inittemplates&nodeName=Templates&rnd=20.2&rndo=21.2' - but only if I tick the box 'Create template for this item'. The same happens when I try and create a Template.
After Googleing I came up with this: our.umbraco post with similar issue. One (unconfirmed) solution is that there's an illegal name in a document type/ template - but I haven't changed anything, and might be fixed by going into the database.
I did check the /masterpages folder, the only 'strange' characters in there are - and _.
In my Document Types I have on named 'Textpage (Two col)' and another named 'News & Events list'. I'm a bit hesitant to just delete them, since I don't have enough Umbraco knoledge to be sure this will fix my issue...
Is there any known solution for this, or will I also have to go into the database (and if so, whereabouts?)
I'm running Umbraco 4.7.2, assembly version 1.0.4500.21031.
I've hosted this site with GoDaddy.com - I don't know if that would be relevant.
[Update 1]
As per Tom Maton's comment:
The requirepermissions should be set to false, and have been.
in Appsettings I've set this:
<add key="umbracoUseMediumTrust" value="true" />
And I've added Trusted_Connection=yes to the connectionstring.
the problem remains.
[Update 2]
Tried the solution amelvin provided, but no dice. Doctypes and templates still give the error. I'm getting more certain it's some security issues. Which folder would correspond to the Templates? Would that be the masterpages folder? If so, what kind of permissions does that one need?
It could be that you don't have full trust on your Go Daddy environment?
Check this post out http://our.umbraco.org/forum/getting-started/installing-umbraco/17856-Umbraco-on-GoDaddy-Shared-Hosting
Could help resolve your issue.
The error could be a knock on from permissions errors as yet unsolved.
But the error is thrown if the content page does not have a template assigned or if Umbraco thinks it doesn't have a template. If absolutely nothing has changed to the site then it could be that the umbraco.config file has somehow got corrupted (it will contain all the doctype/template cross reference info). This can be fixed by right clicking on the top 'content' node and choose 'republish entire website'.
Secondly navigate to the settings | document types (if you can now) and check the templates dropdown on the first tab of the appropriate document type. If its set to 'please select' then this error will get thrown when any page tries to render without a valid template assigned. If a default template is assigned - then go to that template and re-publish it - Umbraco may have lost it.
If this does not work then check if the template is assigned properly. Go to the same place in the content tree as the problem page and try to add a node with the desired doctype. If no choices are offered then it could be that the parent tab no longer allows the correct doctypes as children nodes, so go back to the doctypes and check the allowed children (second tab) of the parent node.
If none of this works without odd errors being thrown then its a mystery!
Here are a list of Permissions required for Umbraco http://our.umbraco.org/wiki/reference/files-and-folders/permissions
Or you could use one of the steps below to check all the folder permissions.
http://our.umbraco.org/wiki/reference/files-and-folders/permissions/perform-permissions-check
Or install this package. http://our.umbraco.org/projects/backoffice-extensions/ugolive this will allow you to check the permissions are correctly setup.
I've been having some issues with my Solr collections, and out of frustration I decided to delete all the folders and start from scratch. I did not remove them via CFAdmin, first.
After some searching, I read where someone suggested copying the contents of the /solr/core0 folder into the collections folders under /ColdFusion9/collections. This will at least make them appear in CFAdmin. However, when trying to index the collection(s), I get the following error:
ERROR unknown_field_author ERROR unknown_field_author request:
http:localhost:8983/solr/dtrparti/update?commit=true&waitFlush=false&waitSearcher=false&wt=javabin&version=1
Is this recoverable without having to re-install ColdFusion 9 from scratch?
Thank you,
^_^
YES! IT IS! According to http://www.elliottsprehn.com/cfbugs/bugs/83331, if you add the following to all affected collection/conf/schema.xml:
<field name="author" type="text_ws" indexed="true" stored="true" required="true" />
.. it will now index.
^_^