Update beanstag shortcut could not get the current path [#1380038]

Hi Chris,

could you take a look on this issue when you have time? i hv a fresh install beanstag and it seems that whenever i click Update beanstag, it will keep showing a cached path until i clear the drupal cache.

Thanks.

Regards,
Kit

Comment	File	Size	Author
#4	beanstag-1380038-4.patch	2.01 KB	foopang
#4

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

foopang CreditAttribution: foopang commented 23 December 2011 at 02:50

Sure, will try to fix that bug. Thanks for reporting this issue.

Comment #2

foopang CreditAttribution: foopang commented 28 December 2011 at 03:03

Sorry Kit, I couldn't reproduce this issue with a fresh install beanstag. Could you provide more details on how the problem accrued? Thanks!

Comment #3

ykyuen CreditAttribution: ykyuen commented 28 December 2011 at 03:29

Status:

Active

» Closed (cannot reproduce)

o, maybe it has conflicts with other modules. let me try to figure out what causes the problem and update you later. thx.

Comment #4

foopang CreditAttribution: foopang commented 28 December 2011 at 10:57

Status:

Closed (cannot reproduce)

» Needs review

File	Size
beanstag-1380038-4.patch	2.01 KB

It's caused by the cache of the Administration menu module. I tried to fix that by storing the last accessed path to the user session without generating a new Beanstag path on every HTTP request.
Here is a patch I made, please kindly review it. Thanks!