LapinChat / dsbudget

Automatically exported from code.google.com/p/dsbudget
0 stars 0 forks source link

Can't open items in budget category to edit after install ver. 2.0.24 in W-Vista #71

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1.Click or double click on items in Budget category
2.
3.

What is the expected output? What do you see instead?

Expect window to open to edit name or amount.  Nothing happens.  It was working 
until I updated to ver. 2.0.24 from 2.0.23.

What version of the product are you using? On what operating system?

Installed 2.0.24-wouldn't work.  Uninstalled and reinstalled-wouldn't work.  
Uninstalled and reinstalled 2.0.23-wouldn't work.  Add new category feature 
works.  Slider works.

OS: W-Vista, Home Premium, SP2

Please provide any additional information below.

Original issue reported on code.google.com by g.d.ro...@gmail.com on 15 Jan 2014 at 6:07

GoogleCodeExporter commented 9 years ago
Ok, so you are able to open your document, but not able to edit it? Since you 
try re-installing 2.0.23.. so I really can't think of any reason why Javascript 
doesn't work on your page. Are you sure the server is running?

Original comment by soichih on 16 Jan 2014 at 3:56

GoogleCodeExporter commented 9 years ago
I have been using DS Budget for 2 years without any problems. This just started 
when I updated from 2.0.23 to 2.0.24. Everything in the Budget program still 
works ok except  no update window will open for existing line items in 
Budgeting category only. Add new category feature and sliders for line items 
work ok in Budgeting category  Other program categories update windows work ok. 

Original comment by g.d.ro...@gmail.com on 16 Jan 2014 at 4:51

GoogleCodeExporter commented 9 years ago
The problem went away after reinstalling ver. 2.0.23 and using it for awhile.  
I don't know why.  I will just stay with this version and not update to ver. 
2.0.24.

Original comment by g.d.ro...@gmail.com on 19 Jan 2014 at 2:05

GoogleCodeExporter commented 9 years ago
Humm.. it could be just some browser caching issue (for javascript or such).

Original comment by soichih on 19 Jan 2014 at 8:46