Forum Subject: Problem The security token when save
Posted on: 11/16/11 11:58am
By: koalasoft
The security token for this operation has expired. If you want to continue with this operation, then please authenticate again below. This will ensure that the changes you just made will not be lost.
and not save changes, I just sent that message and I have to access the site again as administrator.
Note: My version 1.8.1, theme update burning_memory (http://www.geeklog.net/forum/viewtopic.php?showtopic=93345).
Greetings!!
Re: Problem The security token when save
Posted on: 11/16/11 09:05pm
By: Anonymous (ironmax)
I have a problem with the security token, when I go into the administration module, and want to edit for example, the slogan of the site and try to save the changes, sends me the message:
The security token for this operation has expired. If you want to continue with this operation, then please authenticate again below. This will ensure that the changes you just made will not be lost.
and not save changes, I just sent that message and I have to access the site again as administrator.
Note: My version 1.8.1, theme update burning_memory (http://www.geeklog.net/forum/viewtopic.php?showtopic=93345).
Greetings!!
I've tried several browsers and they all work fine...except for Firefox. I have no idea what is causing this issue with that browser only, but it seems to be a bug in Firefox if all the other browsers don't have problems.
Michael
Re: Problem The security token when save
Posted on: 11/17/11 10:38am
By: koalasoft
Greetings!!
Re: Problem The security token when save
Posted on: 11/17/11 11:33am
By: Anonymous (ironmax)
I tried the same with other browsers and I still leave the same message, something else that need to be updated?, certainly in the configuration does not appear blue tabs shown in the Professional theme.
Greetings!!
I cannot think of anything else that can be causing this problem. Usually when updating a theme, you automatically discard the theme's sub-directories and copy over the sub-directories from the professional theme, but not true to all directories is some cases. Like saving the image directory, is one reason. Then you make any needed adjustments to the root core theme files.
Dirk, Can you shed some light on why this is happening?
I did not update the Navbar in the configuration page. So yes it does look like the config insert from the professional theme.
Michael
Re: Problem The security token when save
Posted on: 11/17/11 02:46pm
By: Laugh
Tom
Re: Problem The security token when save
Posted on: 11/17/11 02:57pm
By: koalasoft
Just to confirm, everything works fine when you use the Professional theme?
Tom
If only using the thema pressional all goes well, but we already have a theme we want to update itself, followed your steps, but I sent that message when I save a story or otherwise static page. What else needs to be done to migrate a 1.7 to 1.8 issue?
Dirk .. help !!!
Greetings !!
Re: Problem The security token when save
Posted on: 11/17/11 03:35pm
By: Anonymous (ironmax)
Current Burning_Memory header file
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html {lang_attribute}>
<head>
<title>{page_title} {site_name}</title>
<meta http-equiv="Content-Script-Type" content="text/javascript"{xhtml}>
<meta http-equiv="Content-Style-Type" content="text/css"{xhtml}>
<!-- link rel="SHORTCUT ICON" href="{site_url}/favicon.ico" -->
<!-- <meta http-equiv="Pragma" content="no-cache"{xhtml}> -->
<link rel="stylesheet" type="text/css" href="{css_url}" title="{theme}"{xhtml}>
{feed_url}
{rel_links}
{plg_headercode}
{advanced_editor}
<!-- Load Common Javascript Libraries -->
<script type="text/javascript" src="{site_url}/javascript/common.js"></script>
</head>
<body dir="{direction}">
Modified file
{doctype}
<html{lang_attribute}{xmlns}>
<head>
<title>{page_title_and_site_name}</title>
<meta http-equiv="Content-Script-Type" content="text/javascript"{xhtml}>
<meta http-equiv="Content-Style-Type" content="text/css"{xhtml}>
<link rel="SHORTCUT ICON" href="{layout_url}/images/favicon.ico"{xhtml}>
<!-- <meta http-equiv="Pragma" content="no-cache"{xhtml}> -->
{feed_url}
{rel_links}
{plg_headercode}
</head>
<body dir="{direction}">
Doing this resolved the problem.
Michael
Re: Problem The security token when save
Posted on: 11/17/11 04:04pm
By: koalasoft
just upgrade my current theme in www.koalasoftmx.tk[*1] with this example and the steps I have my theme Laugh personalized updated to version 1.7 to 1.8.thank you very much !!
Greetings !!
Re: Problem The security token when save
Posted on: 11/17/11 04:56pm
By: ::Ben
Ben
Re: Problem The security token when save
Posted on: 11/17/11 05:01pm
By: Laugh
Tom
Re: Problem The security token when save
Posted on: 11/17/11 05:15pm
By: koalasoft
Nice design. How did you build you menu ?
Ben
I took a wordpress design not remember the name, the rest was the inspiration hehe,
who said Templates geeklog is ugly?
Greetings!!
Re: Problem The security token when save
Posted on: 11/17/11 06:15pm
By: Anonymous (ironmax)
I wonder if the problem was that common.js was declared twice. Once in the header and then by Geeklog in the footer (new in 1.8.0). This could have created conflicts when js was used. Geeklog specific javascript files are now added when needed so they do not need to be added manually to the header or footer anymore.
Tom
Did some testing while changing out the top header info and removing the java wasn't the problem. I think it was in the:
{doctype}
<html{lang_attribute}{xmlns}>
<head>
Someplace and haven't figured it out yet.
Michael