First thing to do: download and install the “fixit” plugin from http://markjaquith.wordpress.com/2006/10/28/some-wordpress-205-users-reporting-server-500-error/#comment-5826
It fixes various idiocies with 2.0.5 – while your specific problem may not be mentioned, it certainly can’t hurt to install it.
To the rescue again! Thanks VKaryl! 🙂
Are any of the homepages you linked to yours?
(Maybe one of these days I’ll finish this theme and start actually blogging! Oh well! )
I’ve uploaded the file you mentioned, but I don’t know how to ‘activate’ it? The instruction says to activate..
Regards
Jo
You should place the file in your plugins folder (after uncompressing/uploading uncompressed file – and excuse me if I state things too simply, I never really know how much “net-savvy” people have), then should appear as a normal plugin so you just click “Activate”.
Thanks!
Forgot to post a follow up until now.
I think some of the path issues went away with that fix, but I still don’t *feel* that WP finds scripts and some pictures where I think it ought to…….
I think it would help if I understood WPs file hierarchy better. Is this explained anywhere on the site?
For example, I found a folder containing a number of Javascripts in WP_includes.. What are these scripts, why are they in that particular dir, does WP look there automatically? If so, should I put x.js there, and what relative path should I use to call it…
I guess this post answers your question about whether I am a newbie to web development….. 😉
(ask me about IT project management, or client/server apps though….! the problem is, these things are so boooooring! )
Let’s not mix things 🙂
1. Plugins should always be uploaded to the wp-content/plugins directory.
More: http://codex.ww.wp.xz.cn/Managing_Plugins
2. As for scripts and images path. You can use either relative path (i.e. – /myimages/pic1.jpg) or absolute path (example.com/myimages/pic1.jpg)
Of course, there are certain rules about the correct syntax: a google search might be helpful. It is NOT a WP issue, it is basic html, sorry.
Re: relative paths in WP blogs.
Depending on the rules you learned by the search mentioned above, you’ll realize that in a WP blog there might be “virtual directories”, like when using nice permalinks:
e.g. example.com/archives/2006/12/31/my-fine-post-title.
A wrongly written relative path to the images/scripts might make the browser to look for your images at:
example.com/archives/2006/12/31/my-fine-post-title/imgs/imagename.jpg
which is, obviously, wrong!
Hint: when using relative path –
/imgs/imagename.jpg
or
imgs/imagename.jpg
makes a huge difference!
