|
Author
|
Message
|
|
Richard Bayet
|
Wednesday 02 February 2011 4:45:52 pm
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.
|
|
André R.
|
Thursday 03 February 2011 1: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.
eZ Online Editor 5: http://projects.ez.no/ezoe || eZJSCore (Ajax): http://projects.ez.no/ezjscore || eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription
@: http://twitter.com/andrerom
|
|
Bertrand Dunogier
|
Thursday 03 February 2011 2: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...
Bertrand Dunogier
eZ Systems Engineering, Lyon
http://twitter.com/bdunogier
http://gplus.to/BertrandDunogier
|
|
Paul Borgermans
|
Thursday 03 February 2011 2: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?
eZ Publish, eZ Find, Solr expert consulting and training
http://twitter.com/paulborgermans
|
|
André R.
|
Thursday 03 February 2011 3:56:05 am
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.
eZ Online Editor 5: http://projects.ez.no/ezoe || eZJSCore (Ajax): http://projects.ez.no/ezjscore || eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription
@: http://twitter.com/andrerom
|
|
Bertrand Dunogier
|
Thursday 03 February 2011 5:02:27 am
"
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 ;-)
Bertrand Dunogier
eZ Systems Engineering, Lyon
http://twitter.com/bdunogier
http://gplus.to/BertrandDunogier
|
|
Richard Bayet
|
Saturday 05 February 2011 12:06:44 pm
Hi all,
Thanks for the feedback / reply.
Meanwhile, I'll then post issues on the bugtracker ;) 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. ;)
|
|
Tony Wood
|
Wednesday 09 February 2011 2: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?
Tony Wood : twitter.com/tonywood
Vision with Technology
Experts in eZ Publish consulting & development
Power to the Editor!
Free eZ Training : http://www.VisionWT.com/training
eZ Future Podcast : http://www.VisionWT.com/eZ-Future
|
|
Bertrand Dunogier
|
Thursday 10 February 2011 1: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 ?
Bertrand Dunogier
eZ Systems Engineering, Lyon
http://twitter.com/bdunogier
http://gplus.to/BertrandDunogier
|
|
Tony Wood
|
Thursday 10 February 2011 2: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.
Tony Wood : twitter.com/tonywood
Vision with Technology
Experts in eZ Publish consulting & development
Power to the Editor!
Free eZ Training : http://www.VisionWT.com/training
eZ Future Podcast : http://www.VisionWT.com/eZ-Future
|
|
Bertrand Dunogier
|
Friday 11 February 2011 9:37:03 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 ?
"
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).
Bertrand Dunogier
eZ Systems Engineering, Lyon
http://twitter.com/bdunogier
http://gplus.to/BertrandDunogier
|
|
Andrew Duck
|
Friday 25 March 2011 11:41:59 pm
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.
Andrew Duck, Executive Director, Quiqcorp Limited
eZ Certified Developer and Trainer.
Member of the Community Project Board
http://quiqcorp.com | http://twitter.com/andrewduck
|
|
paul bolger
|
Tuesday 09 August 2011 5:32:21 pm
"
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.
Paul Bolger
|
