This module creates an action for Views Bulk Operations to update per node content access (view/edit/delete etc). It adds a menu item to the Content menu tree and adds a new view which lists content with the VBO action as a button.
The purpose of this module is to offers an implementation of JODConverter.
This module does nothing itself and only provides API for convert files using JODConverter.
Installation :
In order for this module to work, you will first need to set up JODConverter.
Please follow the instructions detailed here.
Usage
Convert a file: $converted_filepath = JODConverter::convertUnmanagedFile('public://doc.odt', 'public://doc.html');
Convert an unmanaged file: $converted_file = JODConverter::convertFile('public://doc.docx', 'public://doc.pdf');
Supported Formats
Microsoft Office to OpenDocument, and viceversa
Word to OpenDocument Text (odt); OpenDocument Text (odt) to Word
Excel to OpenDocument Spreadsheet (ods); OpenDocument Spreadsheet (ods) to Excel
PowerPoint to OpenDocument Presentation (odp); OpenDocument Presentation (odp) to PowerPoint
Any format to PDF
OpenDocument (Text, Spreadsheet, Presentation) to PDF
Word to PDF; Excel to PDF; PowerPoint to PDF
RTF to PDF; WordPerfect to PDF; ...
And more
OpenDocument Presentation (odp) to Flash; PowerPoint to Flash
I was surprised to find that there wasn't a glossary facet that would provide an A-Z listing. I know views offers similar functionality, but thought it would be useful to have as a facet. I've attached my solution here.
This module will create a new Apache Solr index based on the first letter of node title. It then creates a new facet based on that index. Lastly, it strips the count from the items, and adds in any letters missing from the A-Z list so that you have a complete alphabet to display where only the letters that have items will be links.
Some suggestions to make this better would be as follows:
1) Set $glossary_key outside of glossary_facet_apachesolr_index_document_build() so that the name of this facet could be changed more easily. I started playing with this, but it started throwing errors and I don't have time at the moment to fix.
2) I didn't change the way that the facet was being returned at all. This means that in glossary_facet_block_view_alter() this code expects the string returned to be in a certain format. If that changes at some point in a facet api upgrade this will no longer work.