-
-
Notifications
You must be signed in to change notification settings - Fork 825
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Revert merge from master #10277
Revert merge from master #10277
Conversation
…g per payment processor for recurring contributions
…tion with DAO-based approach.
The <value> tag only appeared once in all the schema defintion files thus it seemed to me to be a typo of the (no longer used) <values> tag. Also, I searched CRM/Core/CodeGen/Specification.php for ["']value["'] and found no occurences which makes me think this tag is not parsed.
There were 72 occurences of <type>CheckBox</type> and only 1 occurence of <type>Checkbox</type> So it seemed like "Checkbox" was a typo. Thus I changed it to "CheckBox"
There were 59 occurences of <type>TextArea</type> and only 2 occurences of <type>TexArea</type> So it seemed like "TexArea" was a typo. Thus I changed it to "TextArea"
There were 5 occurences of <change> and only 1 occurence of <modify> So it seemed like <modify> was a typo. Thus I changed it to <change>
…is called on activities. I limited this to activities as there are only 2 separate values & I thought it would keep it readable.
…is called to get contribution_status_id
… function to run the SQL piece. This means that sourceSQLFile no longer has an 'isQueryString' variable, which was used to pass an SQL query in the filename parameter.
(NFC) CRM-20308 Fix Test due to not truncating civicrm_email table
CRM-20459 replace last instances where CRM_Core_OptionGroup::getValue…
CRM-20459 replace all instances where CRM_Core_OptionGroup::getValue …
This will affect new installs only per discussion on the ticket. Motivation dependent, we could add a method to convert on existing installs. Note some fields, like event_start_date might have a case for being in a non-timezone aware format
CRM-20459 replace all instances where CRM_Core_OptionGroup::getValue …
CRM-20435: Replace SQL-based activityContact creation with DAO-based approach.
…eSQLFile_rework CRM-20428: refactored sourceSQLFile
…g contribution, with sales tax enabled
CRM-9683 implement timezone support for CiviMail.
Remove unused var. emailActivityTypeIDs is retrieved twice, statusTit…
CRM-20481 temporarily switch back while we assess / fix performance i…
…nline additional payments
@eileenmcnaughton i think you broke the RC with this c85b067 because it moved it to .20. I believe this correctly reverts that commit pining @davejenx as well |
I think we should probably revert this as well 3c8e8aa |
ug did I - that seems like a very big commit! |
yeh |
Yuck yuck yuck - expletitives! I did have this moment when something wierd happened but!!! |
@eileenmcnaughton i have reverted the other merge from master just as a precautionary measure |
oh - so I merge the wrong way around??? |
@eileenmcnaughton i think so, I think you were hoping to merge 4.7.19 -> master not master -> 4.7.19 |
This seems to be the PR - but is says into master #10266 |
so the overall PR was merged into master but that commit was merging master branch into 4.7,19 and i think its only showing what elements of that commit make up part of the PR i think |
Jenkins test this please |
Jenkins test this please |
After we fix this, I expect folks will habitually resume the practice of forward-porting RC fixes to Feels like we need to either:
|
I think it's confusing because #10266 didn't actually cause the problematic merge, but it's one of the few places where the problematic merge is visible. Pay close attention to the text of the merge message:
Theory:
|
I did have a moment when I was trying to merge something into 4.7.19 & suddenly it was already there - I checked my repos to see if I had pushed to 4.7.19rc but it's set up via https - which means entering a username & password |
No description provided.