headers
Kirk M | 1 Dec 2008 01:58
Picon

404 error using Google Gears in build 9983.

I'm getting an error when using the "Turbo" function with the latest 
"Stay Updated" build (9983) as follows (I auto-updated from 9948 to 9983):

"Local storage status: Error: Download of 
'http://just-thinkin.net/wp-admin/images/tail.gif' failed, status code 404."

"Tail.gif" does not exist in build 9983 nor does it exist in the latest 
trunk build either (9992). However, build 9948 *does* include "tail.gif" 
which I uploaded to my install. Once that was done, Gears downloaded all 
the files (all 261 of them) with no problem. Is there a manifest/index 
type file that tells Gears what it should be downloading that perhaps 
wasn't updated as to what files have and have not been removed?
Permalink | Reply | 2 comments |
headers
Paleo Pat | 1 Dec 2008 02:00
Picon
Gravatar

Re: 404 error using Google Gears in build 9983.

Getting that too... was wondering...

-Paleo Pat
http://www.politicalbyline.com

On Sun, Nov 30, 2008 at 7:58 PM, Kirk M <kmb42vt@...> wrote:
> I'm getting an error when using the "Turbo" function with the latest "Stay
> Updated" build (9983) as follows (I auto-updated from 9948 to 9983):
>
> "Local storage status: Error: Download of
> 'http://just-thinkin.net/wp-admin/images/tail.gif' failed, status code 404."
>
> "Tail.gif" does not exist in build 9983 nor does it exist in the latest
> trunk build either (9992). However, build 9948 *does* include "tail.gif"
> which I uploaded to my install. Once that was done, Gears downloaded all the
> files (all 261 of them) with no problem. Is there a manifest/index type file
> that tells Gears what it should be downloading that perhaps wasn't updated
> as to what files have and have not been removed?
> _______________________________________________
> wp-testers mailing list
> wp-testers@...
> http://lists.automattic.com/mailman/listinfo/wp-testers
>
Permalink | Reply | 0 comments |
headers
Andrew Ozz | 1 Dec 2008 02:12
Picon
Favicon
Gravatar

Re: 404 error using Google Gears in build 9983.

Kirk M wrote:
> I'm getting an error when using the "Turbo" function with the latest 
> "Stay Updated" build (9983) as follows (I auto-updated from 9948 to 9983):
> 
> "Local storage status: Error: Download of 
> 'http://just-thinkin.net/wp-admin/images/tail.gif' failed, status code 
> 404."

Fixed in [9993].
Permalink | Reply | 0 comments |
headers
周子模 | 1 Dec 2008 04:30
Picon

(no subject)

--

-- 
http://seo.mover.com.cn
Permalink | Reply | 10 comments |
headers
Admin | 1 Dec 2008 12:04
Favicon
Gravatar

Re: Bugs/Fixes, Security Requests

Hi - I'm sorry I'm a bit late to this list, but I encountered some 
bugs (w/fixes) in the code - hope it's not too late to add them. As 
well, I had some security requests:

Bugfix:
-------
"Warning: Cannot modify header information - headers already sent by..."

Caused on windows/apache install, when starting with no wp-config.php 
file - auto-creating it adds spaces at end, which gives this message 
(first visible during the install pages). The fix is to change this 
line 158 <at> /wp-admin/setup-config.php to add +b for binary:

$handle = fopen('../wp-config.php', 'w+b');

this prevents the function from defaulting to text format, and 
inserting the extra lines (tested)

Security Request:
-----------------
Remove the generator meta display in themes when called by wp_head(), 
which is the hook set at line 173 <at> /wp-includes/default-filters.php:

add_action('wp_head', 'wp_generator');

Although it can be removed in the theme or via plugin (I did a blog 
post at 
http://activeblogging.com/info/wordpress-security-version-numbers-and-themes/ 
explaining how), broadcasting the version by default seems a bad idea 
- an easy way for a spam program to patrol for older installs (or
(Continue reading)

Permalink | Reply | 8 comments |
headers
Xavier Borderie | 1 Dec 2008 14:56
Gravatar

Contest of the week

http://trac.wordpress.org/changeset/9997
Now who's gonna get changeset 10000? :)

--

-- 
Xavier Borderie
Permalink | Reply | 15 comments |
headers
Kim Parsell | 1 Dec 2008 15:10
Favicon
Gravatar

Re: Contest of the week

Something tells me that the WordPress folks are saving that one for the 
formal release of 2.7. :)

Kim

-------------

Xavier Borderie wrote:
> http://trac.wordpress.org/changeset/9997
> Now who's gonna get changeset 10000? :)
>
Permalink | Reply | 14 comments |
headers
Debra Scott | 1 Dec 2008 15:16
Picon
Gravatar

Re: Contest of the week

is there now a formal ETA for the Formal Release?

On Mon, Dec 1, 2008 at 9:10 AM, Kim Parsell <kparsell-wp@...>wrote:

> Something tells me that the WordPress folks are saving that one for the
> formal release of 2.7. :)
>
> Kim
>
> -------------
>
> Xavier Borderie wrote:
>
>> http://trac.wordpress.org/changeset/9997
>> Now who's gonna get changeset 10000? :)
>>
>>
> _______________________________________________
> wp-testers mailing list
> wp-testers@...
> http://lists.automattic.com/mailman/listinfo/wp-testers
>
Permalink | Reply | 13 comments |
headers
Kim Parsell | 1 Dec 2008 15:23
Favicon
Gravatar

Re: Contest of the week

Not a formal ETA, but read Jane's reply at the end of this thread:
http://wordpress.org/support/topic/219240?replies=3

Sounds like it's not far off.

Kim

-------------------

Debra Scott wrote:
> is there now a formal ETA for the Formal Release?
>
> On Mon, Dec 1, 2008 at 9:10 AM, Kim Parsell <kparsell-wp@...>wrote:
>
>   
>> Something tells me that the WordPress folks are saving that one for the
>> formal release of 2.7. :)
>>
>> Kim
>>
>> -------------
>>
>> Xavier Borderie wrote:
>>
>>     
>>> http://trac.wordpress.org/changeset/9997
>>> Now who's gonna get changeset 10000? :)
>>>
>>>
>>>
(Continue reading)

Permalink | Reply | 12 comments |
headers
Jacob Santos | 1 Dec 2008 15:31
Gravatar

Re: Re: Bugs/Fixes, Security Requests

See reply below previous messages.

Admin wrote:
> Hi - I'm sorry I'm a bit late to this list, but I encountered some 
> bugs (w/fixes) in the code - hope it's not too late to add them. As 
> well, I had some security requests:
>
> Bugfix:
> -------
> "Warning: Cannot modify header information - headers already sent by..."
>
> Caused on windows/apache install, when starting with no wp-config.php 
> file - auto-creating it adds spaces at end, which gives this message 
> (first visible during the install pages). The fix is to change this 
> line 158 <at> /wp-admin/setup-config.php to add +b for binary:
>
> $handle = fopen('../wp-config.php', 'w+b');
>
> this prevents the function from defaulting to text format, and 
> inserting the extra lines (tested)

I don't think writing text is binary, but okay. It isn't about that, as 
it is about the new line character. I've been using the 
wp-admin/setup-config.php and not once has it created an extra newline 
where it shouldn't. Would be nice to do it, if it works and fixes the 
problem.

> Security Request:
> -----------------
> Remove the generator meta display in themes when called by wp_head(),
(Continue reading)

Permalink | Reply | 7 comments |

Gmane