The Commons Events feature depends on RDFa and Schema.org, but our intranet site doesn't need these features because no events are ever published publicly on the open web, so annotated markup isn't a necessity for us. It looks like the Schema.org integration is really an optional enhancement, rather than a hard requirement, so could we simply make these dependencies optional instead of a solid requirement?

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

quicksketch’s picture

AFAICT, it's only commons_events.info that depends on schemaorg and rdf modules. Removing the dependency lines in commons_events.info allows these modules to be disabled, with no detrimental effect except removing the corresponding meta attributes from the markup.

Devin Carlson’s picture

Version: 7.x-3.4 » 7.x-3.x-dev
Status: Active » Needs review
FileSize
585 bytes

RDFa support is optional so I don't see any issues with removing the dependencies on RDF and Schema.org.

Devin Carlson’s picture

Status: Needs review » Fixed

Retested #2 and was able to remove the RDF and Schemaorg modules without any issues or errors.

Committed #2 to Commons 7.x-3.x.

http://drupalcode.org/project/commons.git/commit/8a231dc

quicksketch’s picture

Thanks!

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.