Contents tagged with Orchard
Crowdin: Managing translations for Orchard
Earlier this year the decision was made to shut down the localization tool on orchardproject.net for technical reasons. We had a couple weeks of "downtime" in that state during which we could download the translations we had before, but there was no way to edit or update them (other than doing it manually, which is a tedious and error-prone task). Unfortunately writing a new tool that suits our requirements for managing translations was a no-go due to the lack of development resources in the community (time, most of all) - though it turned out that it was not a bad thing at all!
Changing the content type of existing content items
So you've got a bunch of Page content items in your Orchard instance, but nowadays Orchard is getting popular and everybody has Page content items. But you started to use Orchard before it got cool and Pages are now too mainstream. How can you make your existing Pages unique again? Well, you could change them to use you very own content type, BakelitePage!
Features of Orchard you've never used: Reports
Did you know that there is a module (and a Core module!) in Orchard called Reports? Probably you did because since it's always enabled, you always see its menu item on the admin site. But have you used it at all? Ah, so you haven't either! Let's change this by shortly looking at how it works.
Adding a custom model binder to Orchard
An undocumented extensiblity point of Orchard is that you can add custom MVC model binders in an Orchard-y way, with providers. We needed this for adding the ability of parsing floats with a decimal dot and comma equally well, and it works as following.
Migrating content part data to the infoset - upgrading your module to be Orchard 1.8 compatible part 2.
So you've already upgraded your Orchard module to be compatible with the upcoming 1.8 version. Since your parts now use the infoset to store data you also removed some records. But how to migrate data from the old database tables, that are otherwise not needed and should be removed? Let's see.
Upgrading your module to be Orchard 1.8 compatible
So what should I do with my module to make it 1.8 compatible? Although 1.8 is not yet here (1.7.2 just released) it's not too early to deal with this question, since without intervention your modules won't even compile with the latest (soon-to-be 1.8) Orchard source.
A harsh reminder that you can't forget what's below the abstraction
I've created a content part that had an innocent little property called Index (what, for the historical accuracy, was of type int), and below that there was a similarly named property in the part record. Guess what I got when I tried to use this?
Orchard University course in the 2013. spring semester ended today
As you may have heard, the Orchard Hungary Team hosted a university course at the Óbuda University's John von Neumann Faculty of Informatics this semester. The course started in the middle of February and ended today with the "final" 9 participants (forming 5 teams) presenting their projects. Let's see them in the order of presentation:
Orchard PHP scripting demo at Óbuda University
Moving Tenants across Orchard instances
A few days ago I was facing the task of "merging" two Orchard instances (both of them containing two tenants) into one. As a matter of fact I thought I was looking forward to a raging storm of errors but it turned out to be quite simple. There are two basic rules you must keep in mind: