Custom Browse 2.8, sc 7.3.3 - 26751, Debian/unstable, can not add menu - permission problem

[GoogleCodeExporter]

Which plugin is the bug/enhancement related to ?
CustomBrowse

What version of SlimServer/SqueezeCeneter are you using? On what operating
system?

Version: 7.3.3 - 26751
Operating system: Debian - EN - utf8
Platform Architecture: i686-linux
Perl Version: 5.10.0 - i486-linux-gnu-thread-multi
MySQL Version: 5.0.51a-24+lenny1

Problem: Can not create new menu.

What steps will reproduce the problem?
2. add erland pluing repo listed at
http://wiki.slimdevices.com/index.php/SqueezeCenter_Repositories
3. install CustomBrowse (2.8) via Extension Manager 
4. follow steps at
http://wiki.slimdevices.com/index.php/Setup_new_browse_menus to add Birates
menu
5. at step 8 (click Save), error is returned:
Error:
Error saving: Permission denied

Original issue reported on code.google.com by toni.p...@gmail.com on 10 Jun 2009 at 1:24

[GoogleCodeExporter]

if there was an error message in any of /var/log/squeezecenter, it would be 
easy to
solve this.

Original comment by toni.p...@gmail.com on 10 Jun 2009 at 2:30

[GoogleCodeExporter]

Corrected so its shown which file it fails to write with full path.
Will be included in Custom Browse 2.9pre4 and later releases.

If you enable debug level logging of Custom Browse you will see a message in the
server.log before the error that tells you exactly which file it fails to write 
to.

Original comment by erlan...@hotmail.com on 8 Aug 2009 at 10:16

• Changed state: Fixed
• Added labels: Plugin-CustomBrowse, Priority-Low, Type-Defect

[GoogleCodeExporter]

Thanks for the fix.I did solve the problem there and then, but it took me a 
while, as
opposed to minutes - which is what will be possible now with error showing 
which file
causes the permission problem.

I would suggest you add last sentence from your comment 2, or something similar 
in
your FAQ, or Readme file, so that people who are less technical can have some 
idea
what to do when permission problem happens i.e. to tell them explicitly 
something
like: "if you get a permission problem, enable debug level logging of Custom 
Browse,
check server.log to see which files are causing the permission problem and 
correct
permissions".

Original comment by toni.p...@gmail.com on 8 Aug 2009 at 10:51