|
Thank you for your answer.
I now understand your point of view, and how the component works. I would like to explain our situation so that you might help us find a solution (if a solution actually exists).
We are a record company, and we manage the Web sites for the company, the labels, and the different artists. When we publish an article, we have to duplicate it between two or more Web sites, and each site must have the ability to search articles based on the tags, the sections, and the contents.
We wanted to manage the articles from the Company Web site, but now we understand that it would not be possible. We will have to manage the articles from the single artists' pages, and then pull it to the Labels' sites and the company's site. This is not quite working for us, and we hope to find a better solution.
edwin2win wrote:
The Article Sharing for JMS work as a PULL and not as a PUSH because we consider that this is the reponsability of the owner of the slave site to decide what it display.
Being the owner of both the master site and the slave sites, the responsability is not really an issue. I understand that the module has been built with the idea that the master site and the slave sites were managed by different people. However, I presume that we are not the only company managing multiple sites at the same time; therefore, I suppose that this issue has been already addressed by someone...
edwin2win wrote:
In addition, make the reverse is far more complex as you it would be required to have the list of the websites where you could decide amoung the list the set where you want to push the article and that would be converted by update in all the slave sites selected by something special to read the list of articles that you would have selected.
I know that the ability to PUSH and article is quite more complex than just pulling the information from a master site. The problem with pulling an article is that not all the information are shared between the sites. I also understand that not all the information can be shared with a PUSH functionality since the component can not know all the different functionalities added to Joomla (for example the tag plugins or other content-specific plugins).
edwin2win wrote:
If you want to do PUSH, you just have to create section and categories corresponding to each slave sites and assign the article to this section/category.
In the slave site you will just have to read this section/category.
This solution has some limitations.
First, contents can be assigned to just one section/category; therefore, you have to create a category for each site and then copy the article to all the categories you want that news to be shown. Also, articles shared this way cannot be searched (but this can be fixed by using your search component it seems), and some information are not shared such as tags, comments, and so on. As I said before, I know that sharing content-specific information provided by third-party components is not possible; however, being able to push the content's basic information and then adding the specific ones site by site, would still be of great help.
edwin2win wrote:
It is not planed to develop such complex PUSH.
I would like to suggest to at least consider it.
edwin2win wrote:
The advantage of the PULL is that you have just one site to select (read) instead of multiples sites to write (push).
In addition, in terms of security, the person who is responsible of the slave site keep the control.
If the resposibility might be an issue if the sites are managed by different people, it is not quite the same if you are managing multiple sites at once. It is possible to copy and paste the contents from one site to the others, but having a centralized management of the articles would be a great asset.
Thank you.
|
Forum
