Closed (fixed)
Project:
Entity Registration
Version:
7.x-1.x-dev
Component:
Registration Core
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
26 Feb 2013 at 20:04 UTC
Updated:
29 Aug 2013 at 22:21 UTC
Jump to comment: Most recent file
Comments
Comment #1
mrharolda commentedPatch also applies cleanly to registration (7.x-1.1) and solves the warning.
@caktux, please set the status of an issue to 'needs review' if you attach a patch!
Comment #2
knowledges33ker commentedMrHaroldA,
What did you change in the patch file (if anything) to apply this to 7.x-1.1? I tried patching the module and got the following error:
Ashleys-MacBook-Air:registration ash$ patch < registration-strictwarning.patch --dry-run
can't find file to patch at input line 5
Perhaps you should have used the -p or --strip option?
The text leading up to this was:
--------------------------
|Index: includes/registration.forms.inc
|===================================================================
|--- includes/registration.forms.inc (revision 4702)
|+++ includes/registration.forms.inc (working copy)
--------------------------
File to patch: c
Comment #3
mrharolda commentedWell ... did you? ;) Please try -p1.
Comment #4
mile23It's generally much easier with git anyway:
Speaking of which, here's a re-roll.
Comment #5
mrharolda commentedIt's not changed functionally, so setting it back to RBTC.
Comment #6
knowledges33ker commentedI tried a couple of -p options but I'm fairly new to all of this so I don't think I did it correctly. Is the patch file supposed to be in the main folder for the registration module or in the includes folder? Maybe that is where I'm getting stuck.
Comment #7
mile23Generally the patch file should be in the project folder, at the top level.
Also, I set my patch to 'needs review' in hopes that the automated test would run. I guess that's not enabled for this project.
Comment #8
knowledges33ker commentedThanks, Mile23! I'll give it a try today. I have no idea about the needs review -> automation but I hope that it gets reviewed ;-)
Comment #9
rerooting commentedPatch applies fine for me!
Comment #10
kclarkson commentedI was receiving the same error in the COD Distribution. Patch applied cleanly please commit :)
Comment #11
knowledges33ker commentedPatch applies for me and resolves the issue.
Comment #12
thomas cysPatch works like a charm. Thanks!
Comment #13
retrodans commentedWorked well for me too
Comment #14
levelos commentedAlready fixed in 2852f18a543328ec47e27d6f4ea59ef879153218.