cindreta Posted May 19, 2011 Share Posted May 19, 2011 So i have this CMS that is used by lots of users and generally they do have rights to edit each others article. So now i'm thinking how can i at least warn them that somebody else is already editing it. Just that. maybe with sessions? but what happens when a user just closes the windows, will it destroy it. i taught about storing the value to mySQL but again what if the user closes the windows and so on. i never did this and i could use a boost. thanks guys Quote Link to comment Share on other sites More sharing options...
Stooney Posted May 19, 2011 Share Posted May 19, 2011 Each time the article is edited, increase a dedicated field in the db by 1. when someone goes to save changes, check to make sure that number is the same. If it's higher, that means someone has saved changes while the user was himself was editing it, and you can warn them that they're about to save over changes not included in their document. As far as warning them while editing it, you could use a similar system, combined with ajax, to check every 60 seconds or so to see if there has been any activity with the article. Quote Link to comment Share on other sites More sharing options...
cindreta Posted May 19, 2011 Author Share Posted May 19, 2011 Yes, i taught something similar. but it always comes back to what if the user just closes the window or a tab and doesnt eaven save anyhing. the database will still have a record that somebody is editing. i saw that wordpress has something similar but i couldn't figure out how exactly did it. they show you a message when you open up an article for editing saying that "username is editing the article...". you think it could work with sql only? thx for a fast replay btw Quote Link to comment Share on other sites More sharing options...
AbraCadaver Posted May 19, 2011 Share Posted May 19, 2011 Either do it as previously stated, or set a column in the db called locked when it is edited and if someone else tries to edit it don't let them. In addition, decide on an amount of time that is reasonable to edit, then set the edit time in the db. If the next person tries to edit and it is locked but the time has expired then let them edit it. The ajax route might be a good idea as well. Quote Link to comment Share on other sites More sharing options...
cindreta Posted May 19, 2011 Author Share Posted May 19, 2011 yes maybe the best thing to do is your idea. get the time when a person opens the article edit, increment that time by let's say 5 minutes and store it to the database for that article. This way nobody can edit the article in the next 5 minutes, it sorta works like a queue, i can also tell the second user that he will be able to edit it in 5 mins or if the current user hits save before the 5 mins i can check with ajax if something changed. i guess this can work. its more of a hack than a solution ; ) i thought it's gonna be something extra complicated. thank you for ideas. Quote Link to comment Share on other sites More sharing options...
jcbones Posted May 19, 2011 Share Posted May 19, 2011 Using AbraCadaver's suggestion, then dis-able the edit option, until either the timeout expires, or the user has finished the edit. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.