Hi,

I'm new to patching - In fact, today I did the first patching with this module (as per instructions) and it totally broke my localhost sandbox site with the following WSOD:

Warning: require_once(./includes/common.inc) [function.require-once]: failed to open stream: Permission denied in C:\wamp\www\patchtest\includes\bootstrap.inc on line 921

Fatal error: require_once() [function.require]: Failed opening required './includes/common.inc' (include_path='.;C:\php5\pear') in C:\wamp\www\patchtest\includes\bootstrap.inc on line 921

Here's what I did:
I run Windows XP. My test site is on my wamp localhost and I called it "patchtest" (a brand new clean install of Drupal 5.7)
I also enabled the CDN module.
I installed Cygwin, put the d5_file_url_rewrite.patch in the root directory (c:\wamp\www\patchtest)
Then I went to my cygwin, changed the directory to my root directory and ran the following command:
patch -p0 < d5_file_url_rewrite.patch

there were 4 messages in Cygwin:
patching file includes/common.inc
patching file includes/file.inc
patching file includes/theme.inc
patching file modules/system/system.module

Afterwards when I went to my firefox browser localhost/patchtest

All I can see is the WSOD that I described above... and the site is now permanently broken.
running the -R comand didn't help.

(the pity is that I also did this on a sandbox site where I keep the exact configurations of my live site, and it looks like I will have to rebuild that sandbox from scratch).

So... did I do something wrong? or are we to assume that this module is very far from being usable?

thanks

Comments

wim leers’s picture

Assigned: Unassigned » wim leers
Category: bug » support
Status: Active » Fixed

It doesn't scale yet. But it works just fine. It's running live on wimleers.com and drupalbin.com at this very moment, and has been running on both sites for 1-2 months.

There's only one problem with your test site:
Warning: require_once(./includes/common.inc) [function.require-once]: failed to open stream: Permission denied in C:\wamp\www\patchtest\includes\bootstrap.inc on line 921

You, or Cygwin, have accidentally changed the permissions on includes/common.inc. This is what prevents that file from being included, and since it's a required file for Drupal to bootstrap, you're getting a WSOD.

Just look at the permissions in includes/bootstrap.inc, mimic these permissions for includes/common.inc, and it'll work again :)

drupalina’s picture

Hi,
I'm looking at both files in my Windows XP (right-click -> Properties)
For both bootstrap.in and common.inc the permissions are the same:

Read-only [unchecked]
Hidden [unchecked]

Could it be that the problem is elsewhere?

thanks

drupalina’s picture

Status: Fixed » Postponed (maintainer needs more info)
wim leers’s picture

Those aren't permissions. Permissions are things like "user X can only read and write to this file", "user Y can read, write and execute this file", "group Z can only read this file". I have never set them up on Windows though, so it'll be up to you to figure that out.

Again, this can't be Hierarchical Select's fault. It's probably due to a glitch in Windows, your webserver, or cygwin.

haagendazs’s picture

I just ran into the exact same problem and fixed the issue by changing the permissions to read/write by anyone for that file (of course, that's only advisable if you're on localhost). Try chmod og=rw [patched_file]

Joanzo’s picture

oh my gosh.. you just solve all my patching problem
i try to find the problem of my patching method
is it from the .patch problem or my patching method
but i can't find it until i find this chmod og=rw [patched_file] of yours
haagendazs thanx a lot

grah’s picture

Status: Postponed (maintainer needs more info) » Fixed
Anonymous’s picture

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.

bomarmonk’s picture

Very good, Daniel: my patched file permissions were also giving me a headache and your comment in #5 really saved me from banging my head against an immovable object :)

lee20’s picture

Running the patch command using any patch was causing this permissions issue for me. Found my resolution here: http://drupal.org/node/60116#comment-1196460