Hello Brett,
Simple bug, with the 1.7 beta release. Whenever i click on the blogs plugin:
"mod/blog/everyone.php".
It shows the token error.
Regards,
Uddhava dasa
info@elgg.org
Security issues should be reported to security@elgg.org!
©2014 the Elgg Foundation
Elgg is a registered trademark of Thematic Networks.
Cover image by Raül Utrera is used under Creative Commons license.
Icons by Flaticon and FontAwesome.
Who can upgrade Fusion Riverash do we can try it, please, anything on this!!
@Brett -- "This indicated an incomplete upgrade." -- Always wondered about the elgg upgrade process. Writing over the directory is going to leave dormant files from past versions. I noticed that during other upgrades. I've rather backed up, loaded new fresh elgg, and copied back the neccesary mod, etc files.
@Ron - "Incomplete" isn't correct. I had a phone call between the start and end of that reply and forgot to update it when I realized what was going on ;)
I just made a commit that will handle this better in that the deprecated files will not be loaded, but they will still exist on the server. Probably the best way to upgrade is to do as you describe, but that is a more "dangerous" approach than this. That said, the recommended upgrade procedures will remain to be unzip / upload over the existing directory, but these dormant files will simply be ignored now.
@Brett and Cash - have you seen this token mismatch error on logout?! That's just totally unacceptable!
To duplicate:
This is the error message:
im thinking the best thing to do is to just totally recreate my site one step at a time and not even use the upgrade function, my preference is to not have any orphaned files, so maybe ill just build it one step at a time off of a new install on the side, as each plugin comes available ill add it, then when im done with that ill just hope and pray that i can import my old db and then move it over to production seemlessly...
@Yakiv
token mismatch comes "only" by using "old" themes. You need to copy some files from views/default/page_elements to your_theme/views/default/page_elements. I don´t know at the moment if you need to copy all files, i think the importend files is the elgg_topbar.php!
In your old elgg_topbar.php you find this:
<div id="elgg_topbar_container_right">
<a href="<?php echo $vars['url']; ?>action/logout"><small><?php echo elgg_echo('logout'); ?></small></a>
</div>
if you replace it with this:
<div id="elgg_topbar_container_right">
<?php echo elgg_view('output/url', array('href' => "{$vars['url']}action/logout", 'text' => elgg_echo('logout'), 'is_action' => TRUE)); ?>
</div>
....logout works!
@Brett. You said you just made a commit that will handle this better. And you said the upgrade will remain but the dormant files will be ignored. - I don't understand. Do I need to download a different version of 1.7 Beta to test this "ignoring of the dormant files" - for example, then will the search.php be ignored? Oh what are you saying. I'm not sure what you mean by "making a commit". What good does that do me now? Anything? Or is this for a future version of 1.7? And thus, I still need to delete search.php and other dormant files - cause they could cause problems in the 1.7 Beta I have now? Sorry - I just don't understand. Thanks -Ron
And - let's say I upgrade to 1.7, then 1.8, then 1.9, 2.0, etc. And every upgrade had dormant files. Eventually we could have lots and lots and lots of them, correct? Just wondering.
thanks for the tip cube, i fixed my theme also, excellent appreciate that...
@brett yeah i agree with ron, maybe not now but in the future it will bite us having all those dormant files, maybe in the upgrade doc there can be a list of what we can remove, maybe even provide a simple script to remove those at core level.
@Cube - if you are right, and this "only" comes by using "old themes" then the Elgg 1.7 beta package is using an old theme! I haven't even installed a theme! I am beta testing with the default theme!!!
Maybe you should submit a patch, Cube, since you have a solution?
A“Form is missing __token or __ts fields”error occured when I made featured a group.
- Previous
- 1
- 2
- 3
- 4
- 5
- 6
- ...
- 11
- Next
You must log in to post replies.