Charlie333

Thanks a lot!

One more time – ANY script I DO register with wp_enqueue_script() by action wp_head is rendered in html in wp_footer. My expectations are: script in wp_head are in wp_head, scripts in wp_footer are in wp_footer. But in WordPress 3.9 every script is magically moved into footer. Apart of jQuery – WordPress keeps rendering it in wp_head. My question is – if it has been changed in 3.9 – why there is no trace in codex or anywhere else? Or maybe somehow I have hacked three different WordPress instalations?

That’s the thing. I do like this – in the top of my template file:

function _head(){

 wp_enqueue_style('bootstrap', '//netdna.bootstrapcdn.com/bootstrap/3.1.1/css/bootstrap.min.css');
	wp_enqueue_script('bootstrap', '//netdna.bootstrapcdn.com/bootstrap/3.1.1/js/bootstrap.min.js', array('jquery'));

  wp_enqueue_script( 'jquery' );

?>

<script>
var global_variable={<?php /* PHP code for JSON generation */ ?>};
jQuery().ready(/* some important function also generated in PHP*/);
</script>
<style>

// some css

</style>

<?php

}
add_action('wp_head', '_head' );

Everything goes into wp_head, but scripts goes into wp_footer. So the variable and jQuery call will go wrong as it will stay in the head – and it will go before jQuery and other scripts.

you’re mixing things. design is a one thing. content – like having a custom menu for footer with 100s links is another thing.

you may use the very same design (theme) for a site with 5 footnote links and for another site with bazillions of them. still having the very same theme.

or maybe you have a book-like document in inDesign and what to convert all chapters into separate pages. that would be another story ??

i find funny that you did not understood that using a page/custom template technique is exactly what you are looking for and you what should be using.

on other side – maybe you are looking for totally custom front-end engine, and yes – loading wp-blog-header.php is the way to go.

but first – try to refine what is your object and do you understand the differences between proposed solutions.

That what apofiSS sad is true.
Basically use PNGs for UI elements, and JPGs for photos.

But I have recently read – not sure where, but it was Smashing Magazine I think – that there is a default compression parameter that goes into use when you upload JPGs to media. Suprisily WordPress is recompressing them or so.

Hi Ipstenu,

thanks for reply. I couldn’t try it, as after I posted my question I’ve got so mad about it, I deleted all themes from the server and cleared all fields in database containing “sticky” theme name and thinks still were going wrong. I also noticed some settings in Network were not working as well (could not change privacy settings for blogs) so I thought that something is messed properly. I decide as it’s an early stage of the site to do the very nasty thing – delete and start all over, hopefully never again.

I’ll be more careful with plugins now. Always backup DB first. I still think it is somehow related to wp-ecommerce.