UPDATE command denied
By bajk on Wednesday, 26 February 2020
Posted in JEvents (Free Access)
Replies 5
Likes 0
Views 632
Votes 0
i have 2 joomla www pages with 1 database for both.
first www page has RW user to access to DB, and second www page has RO (read only) user to access to DB. i have installed JEvents plugin. from first page, where is RW DB user is everything OK (here i create, edit, delete events on my page), but from second page with RO DB user if i want to see (only see - view) event from calendar, there is error UPDATE command denied to user 'userRO'@'domain' for table '#__jevents_vevdetail' ... why i need UPDATE command for see/view event from calendar??

thank you form help me
Hello,

You will get the error as we are trying to update the hits record entry. I am a little unsure why you want to provide a read only state for a functional website.

Many thanks
Tony
tonyp
·
5 years ago
·
0 Likes
·
0 Votes
·
0 Comments
·
thank you for reply. is it possible to turn of hits recording? or i must grand only updating this table with RO user for example, bud i dont know if it is possible.
and our situation ... we have 2 sites with 1 DB because - security. one "backend" site (access only from some IP adrresses - restricted area) with RW DB user for insert articles and editing ... and "frontend" site for public reading only with RO DB access. so ...
bajk
·
5 years ago
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello,

You could edit the core code. But then Joomla! will likely have issues with hits too? I would suggest allowing updates by default.

Many thanks
Tony
tonyp
·
5 years ago
·
0 Likes
·
0 Votes
·
0 Comments
·
and wich file (part of code) i must edit/dele to disable UPDATEing table in view/see event? i will do this after every update of course. but i need to disable any WRITE to table things in my "frontend" site
bajk
·
5 years ago
·
0 Likes
·
0 Votes
·
0 Comments
·
ok, i used grant update for nedded table (and column hits) for ReadOnly user and everything is running now
bajk
·
5 years ago
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post