I've posted a topic about this before i think but wanted to check on a few things.
We have a very large number of PDF's, Word and image files in our Intranet site. I users frequently want these files updated. Currently in our version 3.4.1 the only way to update these files (all live) is for me to do this through the admin interface. We don't want the contributors to use the admin interface.
Now as i understand it there is something in Rel 3.6 (comming soon) that you can set an option for MySource Matrix to maintain a friendly url for these files. But in doing this Mysource then serves the file, not Apache, which slows things down some.
There are a few of these files don't require this option to be set but most will as the could possibly want updated at some point.
My questions are:-
Is this correct?
What sort of performance hit are we looking at?
Is there something i'm missing completely about updating these documents?
We see this as the major issue with MySource cause we would prefer to set up the area's and then get the coordinators to totaly control the content but this just isn't possible at the moment.
Thanks for your input
Carl
Yes you are correct. 3.6.0 (out Monday 4th Sept) has a feature where you can tell Matrix to use its own URL rather than the Apache one. This is not enabled by default and must be enabled for each file you want.
The reason is speed. You can take the speed hit if these documents are not accessed too frequently, or if they are always accessed over a fast connection (such as a local intranet). Its very hard to say what kind of hit you will take - but it would be noticable. It all depends on how busy your site is and how good your web server is.
If you do enable the option, you can access the simple editing interface of the file using the standard Matrix URLs (www.example.com/files/word.doc/_edit). You should then use layouts to define how the editing interface should look for File assets.
Thanks for the response. Do you guys see this as a bit of a limitation with your software? and if so do you have any plans on fixing this limitation?
I mean it is a CMS yet it isn't really geared toward updating documents of type pdf, word, etc.
Cheers
Carl
Yes, it is a limitation, but we provide plenty of ways to update documents. The simple editing interface is only for in-context editing of web pages. Documents are a little different, and so we require you use the administration interface we provide.
We understand that the admin interface is a little daunting to the average user and are looking into ways to make it more friendly (and allow you to specify how it should look) but we are still a fair way off in terms of release time.
Thats good that you are looking into ways of making a bit more friendly.
Cheers