Hi guys,

I am having this issue where my default theme is not selectable, this is on my test site so people can view my themes. I didn't realize at first but for some reason chromo doesn't seem as though it can be removed. This is not exactly what I mean.

I have uninstalled chromo and set the default theme to TG-OrangeSlate. However if I clear my cookies and go back to the site or refresh chromo reappears as the theme. TG-OragneSlate is listed as the active theme but cannot be selected. I can switch to the other themes available but still TG-OrangeSlate is listed as the active theme and still I cannot choose TG-OrangeSlate.

I hope this makes sense as my attempts to translate via google very rarely translate properly. That is if I try to translate back from German to English what I have said is completely different then my intent.

Link to site:

Please login to see this link Get registered or Log in

BH  

 

Hi, thanks for report,
I opened a ticket in our BugTracker:

Please login to see this link Get registered or Log in

I have seen  your themes.
I think they are designed for Evo 2.0.7.

Here is a little Upgrade Tutorial for your Themes, to make them compatible:


Open theme.php:

Delete the follow functions:

FormatStory()
themearticles()


Find themeindex() and replace the code with this code:

They are only looking at the main points.
Complete Tutorial will follow ...  

 

Ok,

I have tested this with the latest developer release on our testside:

1. Made Aqua to standard theme.
2. Deleted chromo in stylesadministration
3. renamed chromo folder to chromo-basic.

Inside themesblock all themes were selectable.

Deleted cookies (session and domain). Default Theme Aqua remaind as my standard theme.

What caused errors was this:
1. BEFORE I did anything else, I deleted my cookies.
2. BEFORE calling the side again, I renamed the folder chromo to chromo-basic.
3. This caused fatal error, because theme is available in administration and therefore be selectable from user.

The error on your side isn't ab problem from the block, but a problem from includes/themes.php.
This was changed on 03.04.2010 while the latest downloadable zip-file is from 01.04.2010.
So my changes made afterwards seems to stop your problem.

This files will be available as soon as the latest change (marquee function moved from marquee-tag to mootools function) is finished.

Greetings
Reo  

 

@Spiders ~ I don't understand fully what you are saying. Did some changes get made to the theme format that I did not accommodate for? Are you saying that Story, and article have been degraded? I made the changes you mentioned and they seem to work ok though I still have a couple more themes to update now, thanks Spiders and BTW I like your new avatar much better then the chi one  

@ ReO ~ ok so this issue is on my end? or no?

Thanks as always for the speedy responses

BH  

 

Hi,
there were some changes in the themes. The FormatSTory() and the themearticles() are no longer needed. Their function takes now the themeindex().

Yes, my new avatar is better suited to me :-)

best regards
Spiders  

 

I see that before the change there was an extra table inside of the articles/Story that is now gone as well. This looks much better, thank you for the info sir!

edit: The extra table does still seem to be there in 1536, I made the changes to an older builld at home but had not tested this in the real world at that point. I have now updated Thornz210 but still have the extra table there. Also at the bottom of the news story on the index page there is a nbsp; showing in between Nuke-Evolution and the comment/edit icons.

K .. I'll leave you guys alone  

again thanks for the info

BH  

 

Hi,

I will have time this week to go behind so I will answer you by Email (your offer done) and by having time to help you solving your problem.

Greetings
Reo  

 

ok ReO
no worries there

I will email you some info in a bit to get the last of the reg. process taken care of.

Dave9 / BH  

 

As a temporary fix I have just reinstalled chromo and set it as default, seems to be fine like that.    

 

Hi,

first: kind thanks for sponsoring us a server for one year !!

Second: I have made an installation on this server -> works fine in php5.3 with "register_globals" = Off !!
Because our main-tester kiste0406 tests in php5.3 environment, I do not think, that there will be major differences between the behavior under php4.x and php5.x for the actual version 1618.

If you want to try it by yourself, you can download the latest edition from Sourceforge, which is 2.1.0RC4 Build 1618.

Otherwise (as you now be Tester   ) you hopefully make your tests within our testenvironment on 210test.evo-cms.org

Greetings
Reo  

 

Your welcome, happy to contribute.  

This account allows for add-on domains as well, so if you have hosting coming due anywhere else you are welcome to add them to this account if you wish or need to do so. I know it is a US server but it is very fast and is completely set up for evo. Should you desire it, it is there for you to use.

hahaha I just looked at the SVN and see it has been updated!!

Yes I will make an account over there some time today when I get some free time.    I do still have to have a version running on my site again so people can test my themes but I will start working on the test site for actual testing.

Cheers,

BH

Playing with logos  



edit:

OKay membership had been made awaiting approval is all.  

 

Hi guys .. sorry to double, I am having this issue again. I installed 1618 and it seemed to have been fixed but I installed the latest revision and it appeared again.

As long as chromo is left alone and not uninstalled everything is fine.

What I did:
installed > installed a few themes and made one of them default > uninstalled chromo.

This again caused my default theme un-selectable but would always be listed as the active theme in the theme block. So if you were to change themes to another theme the default would still be the theme name showing in the theme block drop down.

To fix chromo must be reinstalled, made to be default and then the Prior default theme (the one just replaced by chromo) must be uninstalled and then reinstalled. After this everything is fine and any theme can be made to be the Default as long as chromo is installed and active.  

BH  

 

Hi,

I found the problem inside themes handling and fixed it now. Available on 210test.evo-cms.org with php5.3.

I think, that 2.0.8 could run into same problem, because in 5.3 in $_REQUEST the Cookies are included. So the variablename "theme" is got from $_POST or $_GET but overwritten by Cookie variable.

Will be available in SVN and Download after finishing Cookie-Recoding.

Greetings
Reo  

 

sweet..  

Good to have ya back man.

BTW I see that your site evo-cms.org has a bad redirect or something as it is not redirecting to here it is showing a bad db connection.

BH  

 

Yepp ... I have deleted the redirect to make there a new installation.