Open GoogleCodeExporter opened 9 years ago
Original comment by philridout
on 23 May 2012 at 3:35
https://groups.google.com/forum/#!searchin/sites-help-somethingisbroken/google$2
0sites$20comment$20only/sites-help-somethingisbroken/DNbpfAp67SI/Kg3hdHUsecUJ
Original comment by rc...@wbschools.org
on 12 Nov 2012 at 6:25
I'm surprised this is a "Medium" priority issue. I've just started using Google
Sites in a university environment, and the absence of this feature is immensely
frustrating for dealing with large numbers of students (who must be granted
editing rights on other students' content to add comments). From searches, it
appears this has been an outstanding issue for 4 years. Would highly recommend
it be elevated.
Original comment by liam.ma...@gmail.com
on 30 Apr 2013 at 12:19
I stopped using Google Sites completely just because of this issue. Providing
readers with full-page editing access just to allow them to comment is
completely nonsensical. Google doesn't allow it on their own websites and it's
not reasonable to expect us to allow it on ours. Having comment-only access is
a basic function of Web 2.0 systems founded on user-provided content. It's been
possible for at least fifteen years. Not having it is a basic design flaw of a
mission-critical function. Somebody probably got fired over it (or should
have). That they consider this only a "medium" priority is an indication that
Google sees its Google Sites product as only a "medium" priority, which says to
me it's unreasonable for me to rely on Google Sites for anything. It also put a
halt to my expansion into all Google Apps products. I found other products.
Google has made it's choice and I've made mine.
Original comment by j...@beyondthecourthouse.com
on 30 Apr 2013 at 12:48
see this issue also - which better explains why everyone REALLY needs this
function
https://code.google.com/p/google-sites-issues/issues/detail?id=109
if people stopped moaning about no longer using google sites because of this
issue, and instead requested it to be added with a better solution (like adding
a new user level) Google may actually take notice and do something rather than
thinking 'well we can ignore that chap, cus he's now using something else...'
Original comment by Illust...@koolplanet.org
on 8 May 2013 at 11:05
This sucks ass & I hope it gets fixed! =[
Original comment by dvs.sk8e...@gmail.com
on 22 Jun 2013 at 9:09
needs to be fixed
Original comment by f...@silvapiano.com
on 24 Nov 2013 at 7:11
[deleted comment]
Please correct this oversight, it seems like a basic function integral to the
mission of all google products. No idea why this isn't getting more attention
as there seems to be a well developed secondary market to provide this function.
Original comment by novoe2...@gmail.com
on 6 Oct 2014 at 7:01
Why not just embed a Google Group?
Original comment by d...@easygapps.com
on 4 Nov 2014 at 3:54
Embedding a Google Group is impractical. You would need to have a separate
group for each site page that you want comments on (which could be hundreds)
and the comments wont be searchable in the site search.
BTW, the issue has now been addresses by the addition at the Google Apps admin
level to allow viewers to comment on pages.
Original comment by rob.ir...@business.nsw.gov.au
on 4 Nov 2014 at 10:18
Are the Google Apps comments searchable from the site main search engine?
Through the search box on the site root page?
Original comment by Dyn...@gmail.com
on 4 Nov 2014 at 10:23
"Why not just embed a Google Group?"
Google group that is public still requires sign in to post or reply, I just
tested that work around. EPIC FAIL. In addition, I shouldn't HAVE to make a
public group to work around this absurdity. I am trying to promote Google as
our technology platform and if I can't find a way for people to contribute
content without signing in to Google the entire model is another EPIC FAIL.
Help me to help you, Google. Give the users what they want and what is
intuitively expected when we make public sites, groups, etc.
Original comment by Leslie.E...@gmail.com
on 7 Feb 2015 at 1:46
Original issue reported on code.google.com by
stephen....@gmail.com
on 14 May 2012 at 11:21