search

OrchardCMS / Orchard

Orchard is a free, open source, community-focused Content Management System built on the ASP.NET MVC platform.
https://orchardproject.net
BSD 3-Clause "New" or "Revised" License
2.38k stars 1.12k forks source link

Cannot get any third party modules to work with 1.10.1 #6883

Closed donaldboulton closed 8 years ago

donaldboulton commented 8 years ago

Orchard is completely trashed none of you use Orchard so its now a joke. Ha Ha

Skrypt commented 8 years ago

Hey Donald what's up over there ? Did you try installing a module from a fresh installation of Orchard from the source files ? I just did and it worked, I installed the image gallery module.

How are you trying to achieve this ? More details ? Thanks :smile:

sebastienros commented 8 years ago

I assume most modules don't handle 4.5.2 or Nuget packages.

Skrypt commented 8 years ago

We can still get most of them from github, codeplex. Upgrade them, then install them.

donaldboulton commented 8 years ago

That's Right! If you upgrade the modules, I can upgrade almost all but the point is mostly simple web.config errors of not including needed references are breaking 3rd party modules, even the ones built recently. If the below was included most of my argument would be null. References to

  1. System.Data.DataSetExtensions
  2. System.Web.Entity
  3. JetBrains.Annotations, developers like Resharper Even
  4. System.Transactions
  5. System.Runtime

You have lost what a CMS is, that this should be able to be used by anyone, not just developers. All that have responded to this in all do respect have forgotten what is it like for the lesser skilled to have to try to decipher the simple mistakes.

Skrypt commented 8 years ago

I've been thinking about this. I have some ideas for the Orchard Gallery that could evenually fix this.

Skrypt commented 8 years ago

What Drupal does for this is that they manage their own git server wich contains every modules from every contributors. Wich makes them having the right to harvest those repositories to create packages ready to download for each versions of Drupal. They use Tags for that purpose. Though they don't have to deal with .csproj framework configuration changes. On that matter, the Orchard Gallery could automate those tasks through git or github api or else ... we would need to elaborate on that matter eventually if needed.

donaldboulton commented 8 years ago

One thing that got me going was the Gallery links to Modules and Themes have all changed so Me, Orchard Developers and Others have to go through all there past Blog Posts, Twitter......where ever of postings discussions what ever on Orchard and try to fix all the dead links Referencing Orchard Modules or Themes. I know that is alot of rewrite rules or Aliases to fix it but something has to be done. Forget that just one rewrite rule from /List/Modules/ to /Packages/ Moff.Social old and new links. Moff.Social old link: as http://gallery.orchardproject.net/List/Modules/Orchard.Module.Moff.Social Moff.Social new link as: http://gallery.orchardproject.net/Packages/Orchard.Module.Moff.Social

Back to the topic. As of today the References to System.Data.DataSetExtensions is now not removed nor added in web.config @sebastienros sebastienros Fixing dynamic compilation issues 6 days ago 951962f

Orchard 1.10.1 still has 58 Core Modules with References to System.Data.DataSetExtensions in dev, 1.10.1 and 1.10x C:\inetpub\wwwroot\Orchard1.10.1\Modules\TinyMce\TinyMce.csproj(58): <Reference Include="System.Data.DataSetExtensions" />

I removed 1.10.1 web.config reference of <remove assembly="System.Data.DataSetExtensions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" /> I did not add it again like usual. I did not get any Orchard Messages as errors or log errors, so core Modules even with the dead references do not need = <add assembly="System.Data.DataSetExtensions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" /> The core modules seem to work even with the dead reference but most 3rd party modules need it added <add assembly="System.Data.DataSetExtensions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" />