Dotclear Admin cannot handle different browser tabs

[reppep]

I was looking at posts.php for Linkin' Log, which showed 2 posts. In other tabs, I switched to Extra Pepperoni.

I returned to the LL window and clicked the disclosure + for an LL post. I got an error that the post (ID?) didn't exist. When I reloaded, I got the list of posts on EP.

Tabs/windows should 'remember' which blog they're currently associated with.

[sacha]

(In [2664]) sandbox: Expanders continue to work after blog change, see #600 (solved)

[olivier]

r2664 needs more code review.

I'd prefer a system in which a blog change in another tab display a warning in all other tabs with another blog. Could be perform with a check in ajax every minute or something.

Opening many tabs with different blogs is not possible, as a tab stay with the same session.

[biou]

I don't really understand why it is not possible to add a GET parameter with the blog id. With this simple solution, the sessions problems are gone, more restful solution, etc.

[xave]

...and much more room for security problems, nope?

[sacha]

biou, I agree with you, there is two solutions:

• show a warning message when blog is switched in another tab or window
• include everywhere the blog_id parameter, which is more difficult to do:
  • We do it manually, and every Dotclear extension has to be changed
  • We parse internal hyperlinks (in lib.dc.page.php?), and it could be a more interesting solution, but i don't know if it could be quite reliable

[biou]

xave, perhaps, but what kind of security problem ? and do you mean that passing a parameter in a session is by any mean secure ? I am sorry but I do not believe in security by obfuscation.

[xave]

(Changed to a more generic summary)

[xave]

Replying to reppep:

When I select another blog from the upper-right Blogs: pop-up, DC always shows me the Dashboard for that blog. Instead, it should show me the current page (about:config, Users, or whatever I was looking at) for the selected blog.

[bruno]

The only way to handle this feature properly would be to add a query_string parameter to each admin URL and, more impacting, to keep it with each page change.

On the core side, the impact is important, but can be managed. However, a huge effort will be requested for plugins to adapt to new coding rules.

But this improvement would be nice to implement, since it may force plugins to use non-hardcoded urls.

[Tomtom33]

i think it's to heavy for all plugins community. If there is no solution to handle it in different way, i suggest to close this defect