Contents with the Query Tag Node
-
This week in Orchard - 09/06/2019
Announcement, Query, Localization, Documentation, This week in OrchardLots of PRs merged to Orchard Core this week that adds new improvements, fixes, and features. You could also read a demo about the Content Fields Indexing, that is a very useful feature for the developers: they can now query content items based on the value of the fields! Oh, and we will have a meetup soon in Budapest, where Lombiq will giving a talk on Orchard. Get ready for a longer post about these amazing features! We promise: you won't regret reading it!
-
This week in Orchard - 08/16/2019
Query, Localization, Documentation, This week in OrchardMore Razor helpers, advanced Liquid support in GraphQL, a new OrchardCore.Application.Cms.Targets meta package, Full-Text-Indexing and updated milestones for Orchard Core. Want more? Then check out our current post!
-
This week in Orchard - 08/09/2019
SQL Server, Performance, Query, Documentation, Microsoft, This week in OrchardGetting closer and closer to the release of .NET Core 3.0 and Orchard Core RC! What do we need to ship the new version and what are the newest features of Orchard Core? Find out now!
-
This week in Orchard - 07/12/2019
Content management, Query, Localization, Documentation, This week in OrchardLots of new features and improvements and a very interesting demo about the Content Culture Picker is waiting for you in our current post! Oh, and of course our Orchard Core Training Demo Module has got a huge update too!
-
This week in Orchard - 06/28/2019
Query, Localization, This week in OrchardNew queries for GraphQL to return all the configured layers and their widgets and to have access to the site's configured culture settings, and other smaller changes and fixes for Orchard Core are waiting for you in the current post!
-
Checking your infoset data consistency after upgrading from 1.x to 1.8+
Database, Advanced, Upgrade, InfoSet, Orchard 1.x, Orchard 1.8, QueryMany Orchard developers, including ourselves act as early adopters of the Orchard source and use the code from the 1.x and other work-in-progress branches. While it gives us the opportunity to try the new features and get the latest bugfixes, some changes introduce important bugs every now and then. That was the case lately on the 1.x branch, when a problem surfaced regarding the infoset storage: for shifted, versionable content parts the infoset data was not saved in the ContentItemVersionRecord table, but into the ContentItemRecord table instead. Sébastien discovered this issue before 1.8 release and provided a method to fix it, along with a well-detailed description on the Orchard discussion board.