Hi Sarah:
[...]We have a very active Wordpress blog with about 20 bloggers and maybe 100 people who comments. it's open to anyone on our LDAP system and we use the same auth for portal as we do wordpress. [...]
This means that all users in Wordpress exist in Liferay, so all comments (which stores the user email address) can be linked to each user's Liferay account. This is good, as it'll make things easier.
[...]In liferay this blog needs to be open to anyone to view and comment but only this set of people(possibly a user group?) can blog on it.[...]
No problem: this permissions can be configured using a role (just creating a "blog editor" role) and assigning those users that role.
[...] But this won't be the only blog on the portlet. [...]
I guess you mean "portal". No problem: you can have as many blogs as you need. You can scope them to site or to page.
[...]All of the wordpress posts have tags and categories attached to them. So from wordpress posts with authors need to transfer over, tags and categories need to transfer over,[...]
This has been already implemented in Wordpress Importer (for Liferay version 6.0.6). Which version are you using? Tags, categories, pages and entries are correctly imported.
[...]and comments with users associations need to transfer over. It would be acceptable for comments to transfer over with user name attached but not linked to that user in liferay. [...]
This needs to be implemented. The comments' info (user email and comment content) is in the wordpress-generated xml file, so the method that parses that file inside the wordpress importer has to be extended to read the appropriate content and to call Liferay comments services to insert the comments in Liferay's blog entries using the given user's account.
[...]And this has to be finished by the end of the year.[...]
Totally doable. This may take about two days (counting on tests and support for bug fixing) of a java developer who knows Liferay and Wordpress sintaxes.
Ping me if you need more info or some help implementing this.
Regarding your needs about blog entries feeds you may want to use the asset publisher to filter the content that you need (depending on your liferay version you may be able to do more things regarding this), but be open to extend Liferay's blog portlet. You have the tools to extend it's behaviour (hooks, ext plugins) so that they fit your needs. The main thing there before throwing the liferay blogs portlet to the bin is to correctly define your requirements, and after that, look for the best and easiest way to implement it: the community members can help you with that.
I hope I helped you
Regards,
Juan Fernández
Bitte melden Sie sich an, um diesen Inhalt als unangebracht zu kennzeichnen.