Wordpress Themes - WP Forum at BFA

Wordpress Themes - WP Forum at BFA (http://forum.bytesforall.com/index.php)
-   Old Version fixes and change logs (http://forum.bytesforall.com/forumdisplay.php?f=37)
-   -   Atahualpa 3.5.2 released, WP3 ready (http://forum.bytesforall.com/showthread.php?t=8374)

Burn Nov 29, 2010 11:17 AM

I've just upgraded WP from 2.9 to the WP3.0.1 and I dont see any bug with the theme ATA345 at the moment...
If I go for the latest ATA can I upgrade directly from 345 to 353 or should I do some extra steps to make sure things remain stable?

juggledad Nov 29, 2010 11:22 AM

if you are talkng about the menu bug, you won't see it till you go to 353

TheDuckShoot Jan 14, 2011 06:41 PM

I am running Atahualpa 3.4.1 on three blogs and they are woring perfectly. I see no reason to upgrade (don't fix things that ain't broke).

But I am trying to install a new and forth blog with Atahualpa and I tried from versions 3.5.2 to the latest and I cannot get them to work.

All of these blogs are on the same server and starndard themes work with my latest whic is at http://thumbsupmarketing.com. You can see the result.

My main blog using 3.4.1 is this: http://theduckshoot.com/blog that's working fine as you can see.

Can you help please?

juggledad Jan 14, 2011 09:13 PM

Use the 'delete bfa4' button

TheDuckShoot Jan 15, 2011 01:33 PM

Thanks for the reply deleleted 'bfa4' as advised - but no joy
I then added global $templateURI; into the css.php file after #include_once (TEMPLATEPATH . '/functions.php'); as suggested in another post - still no joy
I can't wait to sort this out for this particular new blog but would like to know the solution for the future.

Cheers

juggledad Jan 15, 2011 01:52 PM

what version did you export them from?
you could install the same version in its own folder like atahualpa349, and then import them, then switch to 353
attach a copy and I'll look at them

trusktr Jan 25, 2011 04:54 PM

Quote:

Originally Posted by juggledad (Post 50528)
trusktr - i went back and check the settings file. It shows as one line for me (on a Mac) and it imported fine for me. It could be a machine issue - ie the way the end of line is written cl/lf vrs just lf etc.

hey Juggledad, just to confirm, that indeed was the problem. In linux I was getting multiple lines. I concatenated all the lines together (careful to replace line endings with a space) and everything worked just fine. Sorry it took me long to post, but just so others know, check to make sure everything is one line only.


All times are GMT -6. The time now is 05:41 PM.

Powered by vBulletin® Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.