cancel
Showing results for 
Search instead for 
Did you mean: 

'Unable to save blog configuration details'

ais_todd
Champ in-the-making
Champ in-the-making
I'm using Alfresco 4.2.c (community) running on Ubuntu 12.04 server.

I made a site in Share, added details for a wordpress blog, posted a test comment from within the Share site to the external blog, decided that the URL for the wordpress blog was wrong, changed the blog's URL at my web hosting services, tried to reconfigure the blog within the Share site to reflect the URL change at the web hosting service, and got an "Unable to save blog configuration details" message when I clicked "Save" from within the Share site.

What's up with that?

Thanks for any ideas or suggestions.
5 REPLIES 5

ais_todd
Champ in-the-making
Champ in-the-making
No one else has encountered this?  I tried syncing up another blog for another Share site, deliberately put in the wrong configuration, saved, went back in, corrected the configuration, tried to re-save, then got the same error message as the first blog I tried to configure for the other Share site (OP).

Is there some configuration file somewhere that I can edit so the sites in question go back to thinking there is no blog at all configured?


Thanks for any ideas or suggestions.

ais_todd
Champ in-the-making
Champ in-the-making
Being able to add posts to an external blog from within Share is rather important to my company's business model.  I noticed several old bug tickets about this issue, seems that the bug was fixed.  Except for my particular installation, apparently.

Thanks for any ideas or suggestions.

daballiemo
Champ in-the-making
Champ in-the-making
Same problem here since upgrade to 4.2.c Have not found a solution yet

ratthing
Champ in-the-making
Champ in-the-making
Same problem here.  Anyone??

ratthing
Champ in-the-making
Champ in-the-making
Ok, so I figured out how to deal with this issue.

The alfresco.log file records the following exception whenever you get this error in Share:

<blockcode>ERROR [org.springframework.extensions.webscripts.AbstractRuntime] Exception from executeScript - redirecting to status template error: 08050051 Wrapped Exception (with status template): 080565784 Site containers can not be renamed. </blockcode>

So what I did was:

1.  Go to the Site with the broken external blog configuration, and remove the blog feature from the site.

2.  Go to the Repository, find the Sites folder, then go to the folder for the Site with the broken external blog config.

3.  Delete the folder in that Site's folder called "blog"

4.  Go back to the site, re-add the Blog feature to the Site.

5.  You should now be able to configure an external blog.