5.4.0.5 is now available

Permalink 2 users found helpful
Just wanted to let everyone know that 5.4.0.5 is now available. Not much has changed, except we've fixed the breadcrumb autonav block that a lot of people have uncovered. Additionally, we've added a few more strings that weren't correctly being passed to translator functions, and we've improved the behavior of the login script so that it checks for un-set user attributes that are required during registration. If it finds any, it will make you set those for the account in question upon login.

Please post with any items that you find. We have a few items that people have isolated that can be reproduced around layouts, so hopefully we'll be able to address those soon.

andrew
 
hbartlett replied on at Permalink Reply
hbartlett
Wow, did you skip 5.4.0.4 or did I just miss something...
andrew replied on at Permalink Reply
andrew
We did. We thought a release with "404" in the version number was just a little sketchy for a content management system ;) (we're funny that way.)
elyon replied on at Permalink Reply
elyon
Thanks again for adding core updates from the Dashboard. It's been really great to be able to provide feedback and receive new releases so quickly.
Metaglyphics replied on at Permalink Reply
I've noticed that both this version and 5.4.0.3 seem to break my autonav.

I have a footer in the template:

<?php   
 $bt_main = BlockType::getByHandle('autonav'); 
 $bt_main->controller->orderBy = 'display_asc'; 
 $bt_main->controller->displaySubPageLevels = 'none'; 
 $bt_main->controller->displaySubPages = 'none'; 
 $bt_main->render('templates/footer_nav');  
 ?>


This is an unordered list, and the template renders it like:

item | item | item

When I install the updates, the unordered list is converted to standard bullets with one item to a line.

Can anyone point me towards what I might need to change to prevent this and future updated from overriding my css?

Thanks
andrew replied on at Permalink Reply
andrew
Hmm. That should definitely work. That's how we do the header nav in our dev site (when we're not running the superfish menu) and it seems to render just fine here locally in my machine.

Did you perhaps add the footer_menu.php file to the templates/ directory in the concrete/blocks/autonav/ directory, instead of created a new autonav/templates/ directory in the local blocks directory? If that were the case the new core wouldn't have the footer_menu.php template and it would revert to the standard view.
Metaglyphics replied on at Permalink Reply
Yes, that was it! I'd created the footer_nav template under concrete/blocks/autonav/templates. I didn't realize custom templates should be in the root blocks folder.

Thanks.
ninja182 replied on at Permalink Reply
Currently running 5.4.0.3 and when I try the one button update, it says Upgrade to 5.4.0.3 complete!

It is somehow not picking up the new update and reverting back to 5.4.0.3 instead. Back in the dashboard it still tells me I need to update.

Is this happening to anyone else, anyone know how to fix it?
synlag replied on at Permalink Reply 2 Attachments
synlag
just discoverd when upgrading from 5.4.0.3 to 5.4.0.5 it says upgrading to 5.4.0.3 successfully, but at the sitemap it shows 5.4.0.3, see attached screenshots
okhayat replied on at Permalink Reply
okhayat
Same issue here
okhayat replied on at Permalink Reply
okhayat
Ok. I guess I found the problem. Before upgrading from a 5.4.0.x (2 or 3), the line [code]<?php define('DIRNAME_APP_UPDATED', 'concrete5.4.0.x');?> has to be removed for the upgrade to work correctly.
I did that and my installation is fine.
okhayat replied on at Permalink Reply
okhayat
For the sake of accuracy, I did the upgrade first before I remove this line, and had the issue.
Then I removed the line, went to the Dashboard and found a note that I didn't upgrade my installation yet.
Clicked on upgrade and got the message that we're upgrading from 5.4.0.3 to 5.4.0.5, upgrade and voila!
Hope this helps better
abovecreative replied on at Permalink Reply
abovecreative
Getting the same problem, could you let me know where I find this line so I can delete it.

Thanks
Karl
hbartlett replied on at Permalink Reply
hbartlett
Same issue here too. Where do I find this?
thephilm replied on at Permalink Reply
thephilm
config/site.php
abovecreative replied on at Permalink Reply
abovecreative
Now upgraded, thanks.
okhayat replied on at Permalink Reply
okhayat
Sorry, I didn't have access to reply.
Yes, that's the one, config/site.php
When upgrading 5.4.x.x branches, it adds this line, so you need to remove it, as the update script doesn't seem to do this.
RadiantWeb replied on at Permalink Reply
RadiantWeb
same issue.
andrew replied on at Permalink Reply
andrew
A fix for all of these is to go into config/site.php, remove the DIRNAME_APP_UPDATED constant, go back into the dashboard, and update to 5.4.0.5. This shouldn't happen again - it was a bug in the way 5.4.0 originally wrote the DIRNAME_APP_UPDATED constant

(if anyone follows this successfully then still continues to have problems going forward, please let me know.)
petebp replied on at Permalink Reply
Hi, I got a strange error in the search page...
When I now create a new page with no content the search result shows correctly the page description... when I add a content it shows me a strange thing... see the video...
http://www.youtube.com/watch?v=ev6ychBWqrQ&feature=player_embed...

And I notice again that the search doesn't search in selected areas anymore...
binoy replied on at Permalink Reply
binoy
One of my installs is in 5.3.3.1. Can i upgrade directly to 5.4.0.5? (without installing the in-between versions)?
Mnkras replied on at Permalink Reply
Mnkras
yes
red replied on at Permalink Reply
red
Strange, the upgrade went perfect for me.
Fernandos replied on at Permalink Reply
Fernandos
it went perfectly for me too.

but how would I remove /updates/concrete5.4.0.5 from the url?

Would that work?
$: pwd
$: /var/www/
$: mv /updates/concrete5.4.0.5/ .

and removing the constant
define('DIRNAME_APP_UPDATED', 'concrete5.4.0.x'
from the site.php
andrew replied on at Permalink Reply
andrew
If you're concerned about the version number showing up, you could also rename updates/concrete5.4.0.5/ to anything, as long as you change it in config/site.php. For example, on our hosted sites we named the directories after the dates they're released, instead of the actual version numbers. Perhaps in the future we'll do this so that the actual version number of the release in question isn't so easily reflected in all the URLs on your site.

e.g.

mv updates/concrete5.4.0.5 updates/20100420/

and change DIRNAME_APP_UPDATED TO '20100420'.
braincramp replied on at Permalink Reply
braincramp
This update (from 5.3.3.1) destroyed my page lists. Gone, and I mean gone gone. Strangely some of my pages altogether stopped working as well. Just blank documents no errors or html started. Reverted back to the 5.3.3.1 and all was as it should be.
andrew replied on at Permalink Reply
andrew
braincramp replied on at Permalink Reply
braincramp
Yes, actually I found out that the one page that wouldn't load was because of an external form block that won't allow anything of the page to load (super fun) and the pages returned to pagelists but I had to go to the site map and view properties and save (without changing anything) and they would then appear in the page lists again.

Crazy indeed.
braincramp replied on at Permalink Reply
braincramp
Anyone else seeing this update killing the gallery block? Mine won't allow me to add a gallery and old blocks are broken (running 1.6.3 block didn't fix the problem).
braincramp replied on at Permalink Reply
braincramp
Never mind, some strange database problem was preventing the editing and adding of gallery blocks.
mmgalitz replied on at Permalink Reply
I just upgraded from 5.4.0.3 on two sites. The first appeared to work without a hitch until I tried to edit a block using the HTML edit. I got a window opening to a 404 page not found. Same thing if I tried to access the anchor tool. Once the 404 page window opens it loops back to the homepage and I can't close the window.

The second site, upon opening the edit block using the HTML, I got 500 error messages with a FIXED message. Then the site worked just fine.

Any ideas what went wrong and how it can be fixed? I use the html editing function regularly.

Thanks!
freestylemovement replied on at Permalink Reply
freestylemovement
hi i tried updating from the dashboard and i get this error message :

The following errors occurred when attempting to process your request:

* The directory /home/freestyle/www/www/updates does not exist.

does this mean i have to create a /updates folder inside the /concrete directory or, at the root level? the extra /www throws me off..

also, what is up with my rewrite engine, it's not working all of the sudden, and i noticed that there is no code displayed to paste into your .htaccess file .. i wonder if it's related?

thanks
andrew replied on at Permalink Reply
andrew
Yeah that's weird. It's throwing me off too. Unless you really do have a www directory inside a www directory, that message is wrong for some reason. It probably would be related to the rewrite issue as well.

My advice: remove any DIRNAME_APP_UPDATED constants from your config/site.php file and try updating again.