[Solived] MCPuck file browser not working after upgrade to 0.9.6.3 from 0.9.6.2

[Guest]

Welcome, Guest. Please login or register.
Did you miss your activation email?

1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Kim_dk]

Hi!

I hope you can help me with this:

The mcpuk browser (FCKeditor - Resources Browser) doesn't  show any files or folders after the upgrade.

I upgraded from 0.9.6.2 -> 0.9.6.3

If I try to upload a file, an error message says "Error, "Failed to upload file, internal error..." and when I try to create a folder "You have no permissions to create the folder"

I have checked the folders, and they have 0755 permissions...

Best regards

Kim

[dev_cw]

You need to reset the Resource Path. There is a difference in how the two versions define the Resource Path. You will need to include the full path (as it was prior to 0962) rather than just the relative path. Note:  you will also need to update the settings in the individual manager users if they have custom settings.

[rthrash]

Hmm ... we should probably make an official note regarding this.

[Kim_dk]

Thanks!

It's working great now! Thank you for your quick replies.

Best regards

Kim

[dev_cw]

This is only a problem with updates, new installs work like a charm.

[rthrash]

*wonders if the installer for upgrades could be tweaked to fix automatically*

[OpenGeek]

*wonders if the installer for upgrades could be tweaked to fix automatically*

Nope.  Upgrades should never change existing setting values.  This was just a problem with the way the resource browser was updated to work for a brief period of time (i.e. it automatically appended the base_path to the rb_base_path to get the full path, and stripped the base_path out of rb_base_path automatically if it was specified there).  Should only affect upgrades from 0.9.6.2 and not from earlier versions if I'm not mistaken.

[g5604]

would be great if this was mentioned somewhere a bit less hidden! its a pretty big break and i bet 99% of people will have it happen to them.

[OpenGeek]

would be great if this was mentioned somewhere a bit less hidden! its a pretty big break and i bet 99% of people will have it happen to them.

How is this hidden?  It's in release support for 0.9.6.3 which seems the most appropriate place to discuss it and with a proper subject line... 

[PatrickSamphire]

You're assuming people read the release support, Jason.  They should, but they don't. Hell, I don't half the time. It's dumb, but we're lazy creatures...

[foniksonik]

If it were my choice I'd do a check for this issue and present an error notice on the manager home page... similar to if you have globals on.... Maybe distinguish it somewhat from the other errors by making it a version incompatibility notice or something with a different color or put a border around it or something. Could be a standard way to notify people that a setting is not properly configured (which should only happen during an upgrade, but would be useful regardless).

This would avoid the mistake of changing people's settings (in case they have customized things) but would notify them of the issue. If they are savvy enough to customize things to where they don't want to see this notice every time they log in, then they can go and comment out this notice in the code... or you could make a preference to not show notices.

[OpenGeek]

If it were my choice I'd do a check for this issue and present an error notice on the manager home page... similar to if you have globals on.... Maybe distinguish it somewhat from the other errors by making it a version incompatibility notice or something with a different color or put a border around it or something. Could be a standard way to notify people that a setting is not properly configured (which should only happen during an upgrade, but would be useful regardless).

This would avoid the mistake of changing people's settings (in case they have customized things) but would notify them of the issue. If they are savvy enough to customize things to where they don't want to see this notice every time they log in, then they can go and comment out this notice in the code... or you could make a preference to not show notices.

Sure, I agree, in the next release we could do that.  But until then, you'll have to search in bug reports or release support for this thread when your resource browser stops working after upgrade.

[g5604]

sorry, but an obscure part of the forum.. its a little hidden. 

something which literally breaks all sites, should be highlighted on the download page.

[rthrash]

It doesn't break all sites, though. I'll add a note on the download page, though.

[rthrash]

Better now? http://modxcms.com/downloads