Symphony.

I create a fresh install of Symphony 2.0.7. When I want to edit a section i get a crippled screen:

http://img202.imageshack.us/i/24593284.png/

Further investigation (with firebug) shows me that one file is giving a 404-error:

http://img651.imageshack.us/i/10128548.png/

The file in question is: http://localhost/%5c/symphony/ajax/translate/?Add+item=false&Remove+item=false

And the following JavaScript error:

http://img683.imageshack.us/i/22872910.png/

in file: http://localhost/symphony/assets/symphony.duplicator.js

Anyone knows what’s going wrong? I just created a fresh install from 2.0.7. Disabling extensions did not fix the problem. The Field: Select Box Link-extension even threw a bigger error. Uninstalling this extension still showed this error.

If you downloaded a compressed version from Github, those often fail (missing/truncated files, etc).

I’m chasing a select-box-link bug right now myself, but its server-side.

Did you apply these fixes? http://symphony-cms.com/discuss/issues/view/255/

Ah, those fixes seem to work.

It’s strange however, since I did not download a compressed version from Github. I just downloaded the version on this site on the download-page.

The fix is still missing in the official download package …

Shouldn’t the fix be included asap in the official download package? Just a thought…

Yes. Github confuses me as to which versions are “stable” and which is “experimental” so I tend to download from the site usually.

I tend to download from the site usually.

This should be the standard download procedure. We can’t force people to learn all this git stuff. So I really hope that we will have a working download package on the website soon.

So I really hope that we will have a working download package on the website soon.

We will. The issue is that it’s not really a great policy to silently push changes into the packages post-release. So we’re working on a 2.0.8 release to fix all outstanding bugs. That should be ready soon. But we don’t want to repeat the mistakes of 2.0.7 by releasing it before all known bugs are fixed.

So we’re working on a 2.0.8 release to fix all outstanding bugs.

Great!

It’s probably not “great policy” to sit on your hands with a broken release, either. It doesn’t inspire much confidence that the release version has been a non-starter for two months straight.

Yes.

AFAIK, the team decided to provide a patched (i.e. working) 2.0.7 version very soon. IMHO a slightly patched 2.0.7 release is actually better than 2.0.6. (Yes, I know that some prominent forum members disagree with this. But I have taken all my websites to a “patched 2.0.7” state, which I have described in another thread. It works fine for me.)

A patched 2.0.7 has been released.

The patched release matches exactly my “privately patched” version. I have implemented this successfully on several (=all of my) client websites. So I encourage everybody to:

• make a copy of your website and update this copy
• check everything, especially extension compatibility (which will help extension developers to make ‘em ready for 2.0.8 as well)
• update your live website (if everything works)

Anyone who is starting from scratch should have a good start with 2.0.7 now.

I will try and release my personal list of compatible extensions later today. Maybe this helps, too.