it is true that if another user is editing the item then it will be locked to other users.

 

If you log everyone out and you still see lock icons on the items then there is a problem.
Hanny said:

I thought it was a safety feature - so that if someone is logged in, their articles are 'locked' so they can't be edited/worked on while they may be working with them.

At least that was my understanding of what I saw.

Yes, but I never notice that before.

 

I thought the security is only when the user edit an article, nobody can edit THIS article in the same time.

 

But here, each time a user is connected, all his article are locked in back end Oo

I just test with a fresh installation, if I add an item, even if I'm only an author (item unpublished), it is not blocked in back-end...

 

So what I could change that caused that ? The last thing I do is modify the button save to redirect with the code here : community.getk2.org/forum/topics/k2-add-new-item-window-resize?id=3536014%3ATopic%3A73456&page=13#comments

 

I don't understand, someone had an idea ?

 

Thanks ;)

So, I retry again without the modification in the file form.php, and it works well again :)

 

So the problem really come from the modification :

 

<?php if (JRequest::getInt('step')=='1') { ?>        <script language="javascript">        window.parent.location.reload();        </script>        <?php        } ?>

 

 

Can anybody confirm the problem ?

 

Thanks for your help ;)

I'm surprised to hear it causes that problem.

All that bit of code does is say "If there is an integer that is = 1, refresh the page" it has nothing to do with the locking and/or unlocking of the pages.

 

Also, that code is ran after the database stuff has executed and the article is saved, so I really don't understand how that causes the issue - but if it does, it does.  I'll have to look into it a bit myself - although I can't promise anything because for me it's not a big issue - I don't allow editing of other peoples articles anyway, so if they're 'locked' when that user is logged in I am okay with it. 

 

I'll have to dig around, see what I can find.

 

I know, but it's not so weird :

 

In fact, if you quit the pop-up window with the little cross in top right corner, it's not the same than simply refresh the window.

 

Clicking on the cross or on cancel button do something.

 

When you refresh the window, the popup disappear,but it's not the same than clicking on the cross or cancel button ;)

 

Did you try to see the problem ? It's simple to trigger the problem :

 

Open a page, Log in backend, with admin account.

Open an other page, Log in front end with author account.

Click on "Add an article" on front end, and click on save, your modification quit the popup window and refresh the page behind.

Go in backend, go see your articles list, the last added is locked...

 

 

 

Yea, I understand now.

I'll have to figure out what the close window button is doing (and/or the cancel button) and try to add that code into the if statement. 

That should essentially cure the issue (in theory anyway).  I'll see what I can hack up.

Yes, that's what I try to do this morning, but I failed...

But I did only few tests, so maybe you'll make it, I hope so :)

 

Thanks again ;)

I have to say, almost 7 months after I started this thread, and K2 told me they were going to do nothing about it because I had called them names, and it "is not a bug, just an inconvenience" and people like William White responding again with "use an override", I wonder if now K2 will take a look at this problem? Que inane answers that don't address the problem, like "use an override".

That's the reason I want to fix some of these issues.

So the users who do use this, can stop being inconvenienced.  Isn't that the point of a developer?  To work to remove things that make the user experience inconvenient?  If it wasn't for a few features K2 has that I couldn't find elsewhere, I would be using a different component for sure.  Heck, might have been easier to integrate features the others were lacking, than it is to try and fix this 'inconvenience'.

 

I think to use an other component than K2, but I have already do a lot of modification to adapt K2 to my website, so it would be too long to change to another component. Me too I prefer try to fix the "inconvenience" :)

 



But it is true that the attitude of the developer is rather surprising, and very disappointing...

In fact, to return to the button save problem, I would like to see a successful message in the middle of popup, and for author a message : "Your article was submitted to a moderator, it will be published after verification".
And after few seconds, popup closes.

It will be great, but when I see that just close the popup when we click on save button is very difficult, I'm not very optimistic...


PS : Sorry for my bad english, I'm a french man ^^

I am not here to cause an argument, but as someone looking at this from a different angle with a view to try and find an ultimate solution.

 

Clearly, if anyone started calling names etc, no matter how petty it may seem, most people will just ignore you and not help.  I am not going to go trawling to find out what was said, but if you know you said it, then you cant be surprised at the response. Lets keep thing nice and civil please.

 

Moving forward, William provided a valid solution, use a template over ride, why is that inane?You have someone with a proven track record in K2 community trying to give you advise, so if you dont want a solution to be offered, dont ask the question and the complain about it.

 

In the grand scheme of things, yes it is something that could/should be fixed, but with 1.6 and new features too somethings do get missed.

 

So lets work together as a community here.

If we find a problem, lets work together to test it and prove it.If we find a solution, let works together to patch it.This makes it so much easier to get bugs validated, proved and patched.

SimonK2 Support

 

Jasper Newton said:

I have to say, almost 7 months after I started this thread, and K2 told me they were going to do nothing about it because I had called them names, and it "is not a bug, just an inconvenience" and people like William White responding again with "use an override", I wonder if now K2 will take a look at this problem? Que inane answers that don't address the problem, like "use an override".

Please consider this for one moment.

 

You created this awesome component for Joomla, for free and make it available to the public for free to do whatever you want to with it, for free. A team of community supporters are here, helping for free.

This is embracing open source.

 

However, there will be some bugs that need fixing and the you will work and fix them.

There are some things that some users dont like or would like to see improved that dont affect the function of the component, so will you just stop everything to make this change.There will be some new features requested, would you assessto see if there would be enough deman across the user base to devote more development time or just throw everything at it.

 

I have seen all of these happen many times.

We all would like to see changes, but in most cases, only a handful of the thousands agree they want it.

Developer will work through and make changes themselves.

For those that dont have the skills, there are various forums for help and advise.

For those that have a commercial site, then they will pay for development or support.

Those that dont want any other above, then there is little else that can be offered to help.

 

It would also be hugley beneficial to stick to the topic too.

 

Simon

With all due respect, this isn't considered a bug.  It's an 'inconvenience', that the end users are expected to deal with because it was 'programmed that way'.  At least that's what the thread in the bug section said - is that not the case?

Never before has it even been mentioned that it 'could/should' be fixed - EVER - this is the first time by someone directly involved with it.  The FIRST time. 

That's what I find most frustrating with it IMO.  Only now, is it something that 'could/should' be fixed.  Before it was something that was 'designed that way' and we had just better 'live with it'.  It had been reported as a bug once formally, at least that I'm aware of (maybe more!), and the guy who reported it was talked into just 'living with it' because that's 'just how it's written' and it's 'not a bug'.  He went so far as to post in some of the numerous other threads looking for an answer to this same question stating the same thing that the dev's told him "just gotta live with it", "it was made that way, sorry"  Now there is a different song being sung, why?

 

With regards to a template override being an inane suggestion - I don't think that a template override even comes close to addressing the issue in question... IMO, a fitting analogy would be if someone had a broken leg and was looking for help, and you responded "fix the broken leg". Duh.  What sense does that make?  Now that could be because of my limited knowledge on template overrides (although I understand them in Joomla, and figure the same logic applies).  That doesn't tell the OP what code to add to the override, or even point him in a decent direction to get started learning about template overrides.  Essentially making the answer "use a template override" about as generic as "fix the broken leg", a 'duh' moment if you will.

 

Also you mentioned 1.6, however this bug (can we call it that now?) was documented long before 1.6 was even in RC states, so I don't see how that even plays into it other than to try and soothe some of the ruffled feathers with a politically correct response.  However, I've been in your shoes and I can respect that.

 

I'm not here to argue, as you've probably seen I'm just concerned with finding an answer.  Luckily I've got a few other community members who've taken a chance to test some of my code and found a bug with it already.  Once I fix that, hopefully we can put this whole bloody issue to bed and you guys won't have to worry what to say, you can just go back to saying nothing because it will be fixed.

 

Cheers.

Please see friend request and pm me

Ouch !

 

 

I must admit that it wasn't easy to read everything because I'm French, but I survived :)

So, All I ask is that together we can find a solution, so back to topic :)

I just tried some code but I have each time this lock problem... Grrrr

Thanks again ;)












 

And I forget one little thing, but important : I'm not a expert of K2, so maybe I could find a solution, like Hanny, but we have to spent hours and hours, because We don't know how K2 works exactly, so maybe an expert can help us and we find a solution in few minutes... :)

 

 

Let me please clarify something, my only involvement with K2 is just like everyone else here, we are users.

I am not employed or sponsored by Joomlaworks, just like everyone else here I give my time and experience for free and I have only got involved after some concerned users alerted me to the thread which I was believed to be closed a long tie back after a solution was posted.

 

Hanny, JuJu, I am with you to find a solution.

You do not need to be an expert to help, you do not need to be a coder to help.

All that needs to be done is useful information on any faults, bugs, issues to be reported.By supplying relevant test information, or if you can, code suggestions, then certain members in the forums such as William and myself will discuss directly with the development team.

 

Hanny, there is no different song being sung.

If a dev has said that, then that is what they have said, but, if there are so many people feel that it can be improved or fixed, then why not allow users code suggestions to be posted as an improvement, thats where the likes of William and I could step in and talk directly.

 

The dev team are of course busy developing not just K2 but other projects, so K2 is very reliant on its users and forums.They are not always here to reply to every question, that is frustrating, I know I have had many questions remain unanswered and is one of the underlying reasons why I created simon.getk2.org and now K2Joom.

Its the users, the community that help pull the project together and I cant say that clearly enough.

 

I hope we are working together on this and would happily talk one to one with anyone.

Simon

 

Ok Simon, I didn't know that you're not being part of the developper team of K2 ;)

 

The problem with the Save button is really clear, we want that after clicking on 'Save', the popup box close and page refresh.

 

Hanny find a solution, pretty good, but it cause a problem : The item are not well save, so they are locked by Joomla...

Sure, understand.

I spoke with William earlier too, so know whats what.

Waiting on his next meeting to see if there is solution.

Simon