I'm not really a HTML noob and I do understand from the changelog there is something changed by the way it handles CSS files.

I did an update to 3.4 and it simply doesn't find the CSS file. At least, that seems the case (http://allaboutsketchup.fizion.nl/). I think it has to do with this line:

<link rel="stylesheet" href="http://allaboutsketchup.fizion.nl/?bfa_ata_file=css" type="text/css" media="screen" />

Then again, don't see strange things if I compare it to ither information. Think I do something stupid but can't see what. Hope someone has an answer.

Did you upload all files including the directories such as /functions/ etc?

Does it work if you choose Consigure CSS & JS -> CSS: External file or inline? -> Inline

Well Flyn, thank you so much for that fast reply! Cool!

Unfortunatly changing to inline doesn't make any difference. It shows the same also when I look at the source.

<link rel="stylesheet" href="http://allaboutsketchup.fizion.nl/?bfa_ata_file=css" type="text/css" media="screen" /> 
<title>All About Sketchup</title> 
<script type="text/javascript" src="http://allaboutsketchup.fizion.nl/?bfa_ata_file=js"></script>

I uploaded it all at least, Wordpress did. I uploaded the zip file like stated in the readme.txt to add a theme. I can still choose 3.33 though as installed theme but that is normal I quess because of the different directory names.

One thing that is a bit strange, if I go to appearance > editor. Then I can choose what I want to edit. There is Atahualpa and Atahualpa/Atahualpa34. Don't see why the second option ain't just Atahualpa34.

Please download again, I got it it really mixed up this time, I just uploaded a new version to wordpress.bytesforall.com

Sorry, but same problem. Strange thing (and maybe usefull for you) is that when I go back to default, select 3.4 then the preview is exactly how it should be. But think that does something else then activation. After activation the CSS is lost.

Originally Posted by OzBOz

Well Flyn, thank you so much for that fast reply! Cool!

Unfortunatly changing to inline doesn't make any difference. It shows the same also when I look at the source.

<link rel="stylesheet" href="http://allaboutsketchup.fizion.nl/?bfa_ata_file=css" type="text/css" media="screen" /> 
<title>All About Sketchup</title> 
<script type="text/javascript" src="http://allaboutsketchup.fizion.nl/?bfa_ata_file=js"></script>

I uploaded it all at least, Wordpress did. I uploaded the zip file like stated in the readme.txt to add a theme. I can still choose 3.33 though as installed theme but that is normal I quess because of the different directory names.

One thing that is a bit strange, if I go to appearance > editor. Then I can choose what I want to edit. There is Atahualpa and Atahualpa/Atahualpa34. Don't see why the second option ain't just Atahualpa34.

That Atahualpa/Atahualpa34 thing seems to be because there is already a skin named "Atahualpa", so it tacks on an additional identifier.

Regardless, I'm experiencing this same problem too.

I've actually whittled it down to a couple of things.


Firstly, setting CSS or JS Internal or External does absolutely nothing. The program still defaults to using an External CSS file.


Secondly, the External CSS file won't load properly, if you're home directory for WordPress ISN'T the same directory. Which it's doing for me at least. IE:
http://kojichan.neosouthisland.com/wp/ <-- Where Wordpress is located,
http://kojichan.neosouthisland.com/ <-- Where users actually go.

Because Atahualpa adds it's CSS script onto the end of the URL.

http://kojichan.neosouthisland.com/wp/?bfa_ata_file=css <-- Where it is pointing (Thusly, 404)
http://kojichan.neosouthisland.com/?bfa_ata_file=css <-- Where it SHOULD point (No 404)


Thirdly, Even if you manage to get that far (or view the CSS yourself from that URL), the Atahualpa program DOES NOT use the CSS you painstakingly entered in for hours, but uses it's default CSS code. (Keep in mind, the CSS you entered is still editable via the Theme Option Editor, but it is just not the one being loaded on the front page)

So... Yeah. =/ seems kinda important... In the mean time, I'm going back to 3.2.

Also random... I have this weird glitch in IE 6 that doesn't show in Firefox/Mozilla browsers. My post content format seems to be shifting one pixel to the left with each post on teh page. 1st post has 1 pixel shift, 2nd post has 2 pixel shift, 3rd post has 3 pixel shift, etc. Looks kinda weird........ Not sure what that's about.
(If you have IE 6 you can see the weird glitch here: http://kojichan.neosouthisland.com/ )

'Glad' I'm not the only person experiencing the problem. I also tried the theme on a blog that didn't have any Atahualpa installed before but then I don't experience any problem.

it doesn't do this on a blog with a fresh install? Then it seems it might be something to do with how/where it saves the custom data. I can't find it in the SQL anywhere, so I'm guessing it's stored serverside. Maybe the header file, as far as I've been looking around.

There is a problem with the new CSS INTERNAL setting.

If you use this setting, you will not see any styling you do. IT IS NOT GONE, it's still in the database, so set CSS EXTERNAL, your styling will be back.

So 'play' with 3.4 but do not use the new 'Configure CSS & JS' options.

Okay, I upgraded to 3.4, I made some changes to the site, started noticing problems, came here and learned that we should hold off on 3.4 until some problems with html/css are resolved. So I downgraded back to 3.34.

But...

In 3.4, I set the page-menu bar so that it was centered (a much-welcome enhancement, thank you). But when I switched back to 3.34, which doesn't offer that option, I got an error. In the place where the pages menu nav bar should be, I see only %page-center.

http://www.theagnonschool.org

And I've searched all through my added html/css and the php files can't find where the call to %page-center is stored.

Can anyone help me remove that tag?

Thanks.

Originally Posted by juggledad

There is a problem with the new CSS INTERNAL setting.

If you use this setting, you will not see any styling you do. IT IS NOT GONE, it's still in the database, so set CSS EXTERNAL, your styling will be back.

So 'play' with 3.4 but do not use the new 'Configure CSS & JS' options.

But, I DID try both options of internal or external, and I see the same results, that's the problem..... And, isn't the internal vs external option inside the css & js options regardless? I know the css style is still there,s but there seems to be an issue of it loading on the pages. I can see and edit the information still, but it doesn't seem to want to place the css into the header of the page. Sorry.

Um, I finally figured out where to find the %page-center code. Should ever anyone be as boneheaded as me, you can find it Style & edit HEADER area.

Kojichan
From what I can tell, when you set 'CSS: External file or inline?' to 'Internal' all the styling you get is the default styling. If you set it to External, the styling options you set will work, you just can't see them if you look at the source of the generated page.

If you need to see the styling in the generated source, there is a hack you can use.
Edit functions.php and locate the following IF statement: should be at line 208

	if ( $bfa_ata_preview == 1 ) { 
		add_action('wp_head', 'bfa_inline_css');
		function bfa_inline_css() {
			$bfa_ata_preview = 1;
			include_once (TEMPLATEPATH . '/' . 'css.php');
		}
	}

now add this line before it

$bfa_ata_preview = 1;

this will force the CSS to show up on the generated source of the page.

I've managed to fix the problem myself...

After some farting around, I realized that Atahualpa was using the WordPress function "get_option('siteurl')", which loads the URI for the WordPress Install.

(IE, http://yourblog.com/WordPress/)

Now, because I don't call my blog from that url, it doesn't work for me.
(IE, http://yourblog.com/)

So, instead of Siteurl, use the option Home.


I'm 99% certain that if you call your blog from the same directory as wordpress, this hack will work for you too.
(If you feel uncomfortable editing your files, backup!! I can't stress this enough!)



OPEN: atahualpa34/functions/bfa_get_options.php

FIND:

$bfa_ata['siteurl'] = get_option('siteurl');

REPLACE WITH:

$bfa_ata['siteurl'] = get_option('home');

And viola!! CSS code problem fixed! ^_^ OzBOz, this should also fix your problem, from what I can tell.


Edit: Atahualpa 3.4 introduces some new Widgets, doesn't it? *random* I just had to replace my widgets to "Right Sidebar" from "Right Inner Sidebar"

Hey Kojichan, I tried your trick both my addresses are the same. But unfortunatly it didn't work for me. I hope that Flynn has a nice (bug) fix soon which works for all people having troubles as I'm not the only one.

Originally Posted by OzBOz

Hey Kojichan, I tried your trick both my addresses are the same. But unfortunatly it didn't work for me. I hope that Flynn has a nice (bug) fix soon which works for all people having troubles as I'm not the only one.

Hey OzBOz, out of curiosity, do you have a url redirect or something? Or did you install WP into that directory? (http://fizion.nl/allaboutsketchup/) or is WP in a directory beyond that? (http://fizion.nl/allaboutsketchup/wordpress) ?

*checks* ... OK, so that IS your WP directory.

I wonder if that is the reason why your half doesn't work. The CSS script http://fizion.nl/allaboutsketchup/?bta_etcwhatever=css is being redirected to your index page, so it can't and won't find the CSS. What's your .htaccess like?

Kojichan...

I had the same problem in a newly setup domain. The "$bfa_ata['siteurl'] = get_option('home');" trick fixed everything. Thanks...I did not want to point everything to the wordpress directory.

Originally Posted by Kojichan

I wonder if that is the reason why your half doesn't work. The CSS script http://fizion.nl/allaboutsketchup/?bta_etcwhatever=css is being redirected to your index page, so it can't and won't find the CSS. What's your .htaccess like?

Sorry for the delay but it's:

Options +FollowSymLinks

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /allaboutsketchup/
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /allaboutsketchup/index.php [L]
</IfModule>

# END WordPress

Try the new version 3.4.1 http://wordpress.bytesforall.com/?p=73

Originally Posted by Flynn

Try the new version 3.4.1 http://wordpress.bytesforall.com/?p=73

Hi Flynn,

I tried, and well.. it's more consequent now and shows a site without CSS also in preview. If you need information about my directories etc please let me know. But unfortunatly 3.4.1 still doesn't work overhere.

hEy OzBOz
what version of WP and PHP?

Originally Posted by juggledad

hEy OzBOz
what version of WP and PHP?

PHP Version 5.2.6
WordPress 2.8

Files at my server are located at the allaboutsketchup directory which you can access using http://fizion.nl/allaboutsketchup/ or http://allaboutsketchup.fizion.nl/. In my WP config I use http://fizion.nl/allaboutsketchup as address.

FYI in regards to your question in post#3

One thing that is a bit strange, if I go to appearance > editor. Then I can choose what I want to edit. There is Atahualpa and Atahualpa/Atahualpa34. Don't see why the second option ain't just Atahualpa34.

The reason you see Atahualpa/Atahualpa341 is because WordPress dispplays the theme name as 'themename'/'folder'. If the theme name is unique, the 'folder' is not displayed.

When you say it shows the site without preview, are you talking about when you go to activate the theme or something else?

Originally Posted by juggledad

When you say it shows the site without preview, are you talking about when you go to activate the theme or something else?

Well when I selected the 3.4.01 in my themes it did show a preview -with- CSS. But didn't used any CSS when I clicked activate in the preview layer. In 3.4.1. it also shows the preview -without- CSS. So more consistant, but nett same problem.

Could you give it another try with 3.4.2 http://wordpress.bytesforall.com/wp-...load.php?id=17 ?

I still have no idea where your issues are coming from but I'm sure we'll find out