eZ Community » Forums » Feedback & ideas about the eZ... » Not possible anymore to contribute...
expandshrink

Not possible anymore to contribute directly / post comments on doc.ez.no ?

Not possible anymore to contribute directly / post comments on doc.ez.no ?

Thursday 03 February 2011 1:45:52 am - 15 replies

Hi,

I'm performing an eZ Publish upgrade from 3.6.x to 4.3, using the official documentation.

I must say I really paid attention to the user comments found at the bottom of each step's page : some of those really do shed a light on some misshaps that could happen.

I'm at 3.10.1 to 4.0.7 (3.10.x to 4.10.y) step and - after having some trouble with an official upgrade script that seems to be waiting for a(n existing) patch for some time - I've just encountered the very same strange behaviour of "skipped" / "garbaged" ini files mentionned in a user comment.

As the original comment is not quite clear (I took me a few minutes to figure out it was precisely describing my problem and a solution), I thought I should post a comment to :
a) confirm and acknowledge the bug
b) re-phrase it so that someone being stopped at the exact same step could easily notice the problem

Then, I might have posted an issue on the bugtracker.

(Yeah, that was a long intro)

=> Unfortunetaly, it seems there is no way to authenticate itself on doc.ez.no, hence, to post a comment.
I must admit I'm a step behind on all the "share.ez.no", "community program", "move to github", "ez.no/doc -> doc.ez.no" thingies.
Is there no other way to contribute to the upgrade docs than to post an issue on the bugtracker ?

Regards,
Richard.

Thursday 03 February 2011 10:55:21 am

It was disabled as it was flooded with spam.

The idea was to enable it again by forcing users to login using same login as here on share, but that requires us to setup same login integration on doc.ez.no and that has not been prioritized yet above eZ Publish development.

Thursday 03 February 2011 11:21:24 am

Hi Richard,

I agree that doc comments are an invaluable source of extra infos... it doesn't depend on me, but I have raised the matter again, and I really, really hope it will be fixed eventually. Sorry I don't have a more positive answer...

Thursday 03 February 2011 11:36:16 am

To ez: the flooding of spam typically occurred in bursts in the past, so not a continuous problem. So my proposal that is an extra effort as well: why not open it again and close ad-hoc when there are new spam bursts happening?

Modified on Thursday 03 February 2011 11:36:34 am by Paul Borgermans

Thursday 03 February 2011 12:56:05 pm

It is correct that it was in bursts, but it was increasing in activity.
And we felt it was a wast of our doc personnel's time to spend considerably time every day to try to keep the site clean.

As bd said it's in our backlog and we will push it.

Thursday 03 February 2011 2:02:27 pm

As bd said it's in our backlog and we will push it.

I'm 'bd', for those who didn't make the connection. We like short names at eZ blunk.gif Emoticon

Saturday 05 February 2011 9:06:44 pm

Hi all,

Thanks for the feedback / reply.
Meanwhile, I'll then post issues on the bugtracker blunk.gif Emoticon

Here the first one : http://issues.ez.no/17921

I might post another one for the same migrating step (3.6.x to 3.8.0 / 3.8.0. to 3.8.y ) once I have figured if my own script is better than the - unmentionned in the docs - existing upgrade script (!!) to address the SiteAccess policy limitation value change from signed to unsigned CRC32 issue - mentionned in the user comments. blunk.gif Emoticon

Wednesday 09 February 2011 11:11:12 pm

After reading this thread, it re-confirmed to me that eZ really needs to have better comment / forum management tools.

These need to counter, spam, trolls and inappropriate comments.

This is an issue that most eZ Publish sites have so would be great to see some ideas from the community as to what we develop or integrate to counter it?

Thursday 10 February 2011 10:38:42 am

Hey Tony.

About comments, do you think ezcomments was a good way to go ? We know it isn't as complete as it should ultimately be, but we're not done yet.

For the forums, have you checked the FluxBB extension by Guillaume ?

Thursday 10 February 2011 11:58:15 am

About comments, do you think ezcomments was a good way to go ? We know it isn't as complete as it should ultimately be, but we're not done yet.

For the forums, have you checked the FluxBB extension by Guillaume ?

I think that eZ Publish needs a solid set of basic (and usable) set of Social Media Tools. These should cover Comments, Forums, Ratings, Reviews, Facebook/Twitter login along with management tools for simple member freezing, banning, alert management and team based community management.
The basic set of tools will form a starting point. Then eZ needs hooks to allow other tools to replace the existing tools so you can replace either a single tool or all of them with an entire package like a full Social CRM system.

ps. all forums/comments etc should not be eZ Objects they should be straight SQL tables but still be managed via the eZ Interface.

Friday 11 February 2011 6:37:03 pm

About comments, do you think ezcomments was a good way to go ? We know it isn't as complete as it should ultimately be, but we're not done yet.

For the forums, have you checked the FluxBB extension by Guillaume ?

ps. all forums/comments etc should not be eZ Objects they should be straight SQL tables but still be managed via the eZ Interface.

My point exactly... ezfluxbb connects to a fluxbb instance, and ezcomments (shipped by default) uses dedicated tables to store comments and manage moderation. It also has management for "semi-anonymous" posting (no real eZ user created, but linkable later if wanted).

Saturday 26 March 2011 7:41:59 am

As a short measure to get comments working again it would be nice to have an "Inappropriate" button on comments within the doc.ez.no and essentially crowdsource the reporting the spam comments. It seems to work quite well here on share.ez.no, I don't see why the same approach couldn't be used on doc.ez.no in the short term as it should be easily deployed and enables the community to continue contributing to the documentation.

Wednesday 10 August 2011 2:32:21 am

As a short measure to get comments working again it would be nice to have an "Inappropriate" button on comments within the doc.ez.no and essentially crowdsource the reporting the spam comments. It seems to work quite well here on share.ez.no, I don't see why the same approach couldn't be used on doc.ez.no in the short term as it should be easily deployed and enables the community to continue contributing to the documentation.

To add to that, why not just completely disable html in the comments? Most spammers are either trying to get the user to click on a phishing link, or think that getting links to whatever lame site they are trying to promote will improve their Google site ranking. If they can't post links there's not much reason to spam.

Friday 16 September 2011 4:06:47 am

The reply has been removed because of violation of forum rules.

Sunday 05 August 2012 1:30:17 pm

As an ever shorter measure, as long as you cant login, dont print the "add reply" button. 

And while you're at it, dont print the comments either. They are extremely valuable, especially with the 'share' chant in mind, but only if it works. There are some comments on there that still need clarification, or updating - some are very old! Right now these are only obfuscating the docs. If we were able to comment on that, it would be ok, but I'm afraid that momentum is lost.

I would suggest to remove all comments from < 2010 and open it up again.
And let us users remove the spam for you.

 

$2c,

*-pike

Monday 06 August 2012 11:00:27 am

Hi *-pike, 

All valid comments and suggestions, thanks for sharing your thoughts!

While we might unfortunately not be able to do a lot concerning doc.ez.no on a near-term (slight resource shortage doc-wise), we are seriously envisaging to start using Confluence (Atlassian product, wiki-style) to document eZ Publish 5. The nature of the product will make it easier to contribute to the documentation, and I hope (I need to dig into Confluence feature-list) that I will be able to set-up a community moderation team, just like we have today on share.ez.no (which is working fantastically well).

Cheers,

expandshrink

You must be logged in to post messages in this topic!

36 542 Users on board!

Forums menu

Proudly Developed with from