I have 2.7.1 so just click update automatically and done. Sound simple enough.
Chuck
Mine is updated, did it the day they released it. works great here.
Ok found a problem after upgrading to the new ajax carterlake scripts.
On the wordpress when doing a validation for Valid XHTML 1.0 i get this error now:
Sorry, I am unable to validate this document because on line 277 it contained one or more bytes that I cannot interpret as utf-8 (in other words, the bytes found are not valid values in the specified Character Encoding). Please check both the content of the file and the character encoding indication.
The error was: utf8 “\xB0” does not map to Unicode
Looking at line 277 this is the line it is giving the error on:
48.2
that error is caused by the axax-gizmo.php AJAX gizmo V1.03 Canada/USA/World
You should report that in the new ajax carterlake scripts topic.
Thanks will post over there.
ok found an issue now with a valid xhtml that is coming from the script for the blog, This is after upgrading to 2.8 of wordpress has to do with the search line:
Error in Line 417, Column 28: Attribute “role” is not a valid attribute. Did you mean “frameborder” or “scrolling”?
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the “Strict” document type with a document that uses frames (e.g. you must use the “Transitional” document type to get the “target” attribute), or by using vendor proprietary extensions such as “marginheight” (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute.
Thanks!
form role=“search” is added to wordpress by the developers for accessibility compliance. It is there to assist visually impaired screen readers.
The validator does not recognize the “role” tag, however there is nothing wrong. It is OK.
Accessibility compliance trumps the validator in this situation so say the wordpress developers (I looked at the bug report once, it was closed by the developer).
The validator sometimes lags behind recognizing some of these new accessibility tags, it may be added eventually.
The role attribute isn’t actually in the XHTML DTD yet (although it is part of the HTML 5 spec. It’s only at the Working Draft stage, so, ideally, it shouldn’t be included in an XHTML page just yet. But, that said, it shouldn’t cause any real harm if you don’t want to edit header.php and remove role=“banner”.
Ok will let that alone for now, thanks!
I posted this in an old thread and was redirected here so I will post again. #-o
I followed the instructions on the first page and I believe that the template portion is working fine, but I ran into a couple of issues trying to update my blog tonight.
-
My blog dashboard says that I should upgrade from 2.6.2 to 2.8.4, but when I do, it says that I am up to date and do not need to upgrade.
-
I went ahead and tried to change my pages to the new template format. It went somewhat OK, but I am getting an error in the blog navigation:
Quote
Fatal error: Call to undefined function get_search_form() in /virtual/users/e15586-16411/web/wordpress/wp-content/themes/wxblog/sidebar.php on line 10
The sidebar.php is in the correct directory though.
I believe line #10 is
<?php get_search_form(); ?>- It is also missing the footer.php and all my old blogs. Will this be corrected once #2 above is fixed?
Fixing #1 is the first priority.
If the automatic update does not work, you can manually update. I will not be able to help much with that, but here are some helpful links:
Here is the wordpress support forum link.
http://wordpress.org/support/forum/2
Thanks for the link I will look into it. I posted in the WP forum also, but no reply yet.
I wish I was more help right now, I am kind of busy working 14 hour days.
Working for a living has it’s drawbacks, but I tried not working a few years back and things did not go well at all. :lol:
I found the extended upgrade instructions for Word Press and all is working with the newest version.
FIXED Hi all,
got this error when loading my page. All I did was update the files as shown in the directions for wordpress.
Webpage error details
User Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; OfficeLiveConnector.1.4; OfficeLivePatch.1.3; Tablet PC 2.0; Qwest 1.0; Creative AutoUpdate v1.40.01)
Timestamp: Mon, 5 Oct 2009 00:45:59 UTC
Message: Permission denied
Line: 923
Char: 5
Code: 0
URI: http://www.napavineweather.info/ajaxWDwx.js
:?
James
Help!!! I’ve installed Wordpress and the Wxblog theme and have a serious mess here. I’ve read and reread the instructions, but to no avail. I am open to ANY ideas on how to fix this.
Thanks, John Sacrey
It is caused by WordPress version compatibility.
The theme has only been tested up to WordPress 2.8.6
2.9 came out Friday and the theme has not been tested or updated for it yet.
I am working on it today.
A wxblog theme update will be required when updating to WP 2.9, I have it working on my site now. update coming soon.
Thanks Mike. Appreciate all of the excellent work you do.
WordPress Version 2.9 is out.
It has significant enough changes to require a new wxblog theme update.
A wxblog theme update will be required when updating to WP 2.9
Follow these instructions to upgrade:
http://discourse.weather-watch.com/p/284695
If installing for the first time, look here:
Mike,
Unfortunately that did not fix the problem and I do not know why.
Here is my blog: http://sacrey.info/wxblog
I uninstalled the directory and reinstalled it with no change. Hmmmm…
John
P.S. - I am using the weather-screen-blue-wide.css file with hardly any changes made to it and I opened the page up in IE8 with the same result (using FireFox currently).