Since version 4 the discovery is standard on dspace structure unlike previous versions they had to be activated. It is possible to disable it or hide it? with any configuration without having to modify code or xslt files.
If the goal is to completely disable Discovery, then I think you can do it by following those two steps.
Fist in config/dspace.cfg, you should change the event system configuration: replace
event.dispatcher.default.consumers = versioning, discovery, eperson, harvester
by
event.dispatcher.default.consumers = versioning, search, browse, eperson, harvester
Then, in config/xmlui.xconf, you should enable the old Lucene search aspect (look for the Search Engines section in the document).
A full Lucene re-index will be necessary.
Not tested personally, this should work on DSpace 4 and 5 XMLUI, however.
Cheers,
Benoît
Related
As per the default addressing for a Sitecore multilingual solution, is there a way to change the default addressing, for example
www.mydomain.com/zh/products for a simplified Chinese to www.mydomain.com/sc/products
without altering the sitecore pipeline. Thanks
Without altering Sitecore pipelines or LinkManagers, the only obvious way I can think of achieving this would be to use the IIS Url Rewrite module. You could set up configuration in that, to rewrite some or all of your URLs.
What isn't clear from your question is; if you want to force ALL URLs onto the /sc/ path, or you want to get rid of language embedding in the url unconditionally? If the latter, you can modify your UrlOptions to disable "languageEmbedding" by setting it to "never".
You may register sc language based on the template of zh one on your machine. Then you can rename zh language item definition in Sitecore.
It may work but there could be unknown repercussions as a result. Anyways if you decide to try it out, backup your databases before you start renaming those languages. If it does work and you give it a go, document it for those who'll take over solution after you. They'll be quite thankful for that :).
We are currently running Sitecore CMS 6.5 (120706) with the shared source Item Buckets module installed from here:
https://github.com/jerrong/Sitecore-Item-Buckets/tree/master/sitecorepackages/ItemBuckets%206.5%20NET_40/Final
We wish to upgrade to CMS version 7.0. I'm told that there is currently no upgrade path and to expect one in a few months. However we would prefer not to have to wait on this.
Item buckets is used only for a single section of our site. Everything else is delivered via the standard content tree.
We have tried upgrading to 6.6 first as required by the documented upgrade procedure, despite it mentioning later in the instructions that the shared source item buckets module is unfortunately unsupported for upgrade. Confirmed that this definitely does not work, we receive the error:
Exception Details: System.IO.FileLoadException: Could not load file or assembly 'Lucene.Net, Version=2.3.1.3, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
We also tried disabling Item Buckets by removing the .config files etc. but we had further problems, presumably because of the actual content/data template changes that were made by the Item Buckets update.
We are thinking of trying a clean install of CMS 7.0, and then migrating our custom code base, items in the content tree (including data templates, layouts, renderings, etc) with Sitecore packages to work around the issue.
Can someone validate this approach, or better still suggest a much less painful solution!?
Many Thanks
(this is not official Sitecore advice as that is still being worked on disclaimer,disclaimer!)
Some ideas that might help ..
First we need to work on the data side of things (forget front end code for a second)
You could Un-bucket your items so that they are again plain Sitecore items. You could then remove the item bucket module templates and fields as you mentioned before (by 'unbucketing' you should now have no reliance on the bucketing templates etc.)
You could also look at creating an 'anti-package' using Sitecore Rocks, either way this should give you a site closer to a site before the item buckets module.
You could then get a base/clean install of 6.5 (120706) and then compare it to your working copy 'master' database using a tool like Sitecore Courier.
Sitecore Courier - https://github.com/adoprog/Sitecore-Courier - Allows you to compare 2 versions of Sitecore DB against each other and make an update package of that difference.
This should make you an update package of all the changes that have been made to your 'master' database so that you can, in theory, install this into a fresh copy of Sitecore.
You could see how far this gets you when you install this update package, in theory then you can re-bucket your section that used the old buckets module but using the new built-in buckets.
Front-end code wise, the old item buckets modules way of accessing the search has been completely re-written as that it now uses Linq To Sitecore. Hopefully this will be easier to migrate and the buckets will still work in largely the same way (hopefully better hehe!)
Like Ruud I would be interested to hear about others techniques for doing this.
Any extra complexity could come from thing like :
1) How much customisation of the core database you have done
2) How many new field types and XAML applications you may have written
At this point, there is no good solution for this yet.
If you are actively using the module, there is no way to upgrade right now (not that I know of).
If you are not using the module at all, you can remove everything in Sitecore that has to do with ItemBuckets.
This is a manual job for now... (I've done this with success in a 6.5 environment).
To be sure you remove everything, open the item buckets installation package (the ZIP file) to see what items are installed and manually remove all those items from Sitecore (this will include templates, fields, field types, settings).
You can also use the search in the content editor to search for "itembucket" or "item bucket" and find related items that way.
Another way is to search with SQL directly in the master and core database.
Once you have removed everything in Sitecore and configuration that is related to the buckets, rebuild the link database and run a database cleanup (from control panel) and you should be good to go.
It's a dirty job...
If anyone has a better way, I'd love to hear about it!
the problem you are having there is that the item buckets code was compiled against Lucene.Net 2.9 and Sitecore 7 has v3.0.3.
You could add an assembley binding in in the web.config configuration/runtime section that maps the old version to the new and then fix any issues you get with deprecated methods etc...
You will probably also want to remove the Item Buckets module before the upgrade as suggested as the new bucket templates & items may conflict with the shared source versions. You would at least need to remove the Item buckets config and dll's from the bin folders as these could also conflict.
I don't think there is a simple way of doing it yet or Sitecore would have given out an upgrade path already.
As you may have noticed, the wiki module has been dropped in v7 of OpenERP.
The question is: what alternatives are there it? Is there any community module available or in the works, providing wiki (or even markdown) documents?
For what it's worth, here's a little more info regarding what I said in comments.
In OpenERP 7.0, the wiki module has been renamed/revamped into the document_page module. You may find this mentioned in the last section (8.3 Renamed Modules) of the OpenERP 7.0 Release Notes. It now uses a simple WYSIWYG/HTML editor and stores the pages as HTML, instead of the previous wiki/markdown-based syntax. Therefore you may or may not see it as a true "wiki alternative". The goal is to make it easier and more flexible to use, effectively providing a minimalist CMS system inside OpenERP: you can use it to add static pages in your regular OpenERP menu (or your OpenERP portal), organize them in section/categories, etc., using freely editable HTML (you can edit the HTML source if needed), while preserving their
Note that several issues in the initial 7.0 release might temporarily make the document pages less user-friendly than they should: the WYSIWYG editor was not enabled in all cases in edit mode (fixed now) and the editor is sometimes too narrow (should be fixed soon).
On a related topic, it may also be interesting to know that OpenERP 7.0 provides a collaborative writing solution via the new pad module, allowing you to embed etherpad-lite pads in your documents. It's integrated with the project and the note modules, and you can use it easily for your own custom modules as well.
The OpenERP Knowledge Addons features a module to support MediaWiki syntax (currently only available/verified for v6.1).
I have a Sitecore 6.5 project, where I have upgraded all the content from an earlier version. But something seems to have gone wrong in the upgrade process, which has caused all items to have a security setting of extranet\everyone which have deny read access, even though that is not the case. Also the layout and insert options needs to get reset and taken the values from the templates standard values.
I could do this manually in the Sitecore UI, but that would take quite some time, as there is 3000+ items.
Is there any way I can patch this with a quickfix of some sort?
You could either write a script in ASPX that does this for you or install the PowerShell module and script it with that.
It depends on your experience and on which tools you have available.
Unfortunately there is no built-in method for resetting layouts and insert options on all content items.
We use DokuWiki to manage our internal documentation but the page renames / moves are not supported very well (there is no built-in way other than messing with raw files manually and the third-party plugin 'pagemove' is no longer developed). Which is a pain.
I'm looking for an alternative which will be similarly simple as DokuWiki (must be filesystem-based) but handle the page renames/moves well. Any suggestions?
For anyone whose search lands them on this page - you might also be interested in the plug-in that keeps links for moved and renamed pages in DokuWiki:
http://www.dokuwiki.org/plugin:move
Starting with Comparison of wiki software and sorting them by Data backend, there seem to be quite a few file system based wiki's. Skipping the webpages that are down or incomprehensible turns up the following viable candidates:
MoinMoin
Twiki
PmWiki (after installing a plugin)
JSPWiki
In the end it's up to you to decide which of these best suits your needs & supports migrating your existing contents to the new wiki (no small feat), but at least it's a start.