Removed duplicated licenses and not needed changelog files
This commit is contained in:
parent
5e16eb66dd
commit
c78267142a
80 changed files with 1 additions and 22080 deletions
|
@ -1,149 +0,0 @@
|
|||
CCK 6.x-3.0-alpha4
|
||||
==================
|
||||
|
||||
- Security: Open Redirect - SA-CONTRIB-2015-126
|
||||
- #1401950 by KarenS, Add empty test module with dependency on schema to make schema available to testbot.
|
||||
- #1363036 by markdorison, Fix Class 'ContentCrudTestCase' not found message in tests.
|
||||
- #1097548 by DeFr: Fixed warning on node forms for multigroups without any required fields.
|
||||
- #998494 by zhangtaihao: Fix Node Reference field always displaying 10 results
|
||||
when using the Advanced View option (with Views 6.x-3.x)
|
||||
- #1167004 by DeFr: Dramatically enhance node display performance issues.
|
||||
- #1189090 by gaurishankar, yched: Fixed warnings on multigroups with no
|
||||
required fields.
|
||||
- #1423432 by sun: Fixed testInfo() methods throws PHP notices.
|
||||
- #1533506 by yched: Fixed field tokens not available in hook_update_N().
|
||||
- #1442886 by pdrake: Fixed fatal error "failed opening theme.inc" in some edge
|
||||
cases.
|
||||
|
||||
CCK 6.x-3.0-alpha3
|
||||
==================
|
||||
|
||||
- #1081072 Imagefield validation does not use error_element, needs a tweak so that the empty required field gets highlighted correctly.
|
||||
- #1081072 Imagefield validation requires that we alter the field_info values or it will still require an image in an empty group.
|
||||
- Fix miscellaneous undefined index errors.
|
||||
- #1081072 Tweak fix for required fields inside non-required group so not all fields are highlighted.
|
||||
- #1093928 Required option lists do not have an empty option available. Add one to avoid 'An illegal choice has been detected' errors for empty groups.
|
||||
- #1081072 Fix Cannot use a scalar value as an array problem when using optionwidgets.
|
||||
|
||||
CCK 6.x-3.0-alpha2
|
||||
==================
|
||||
|
||||
Features:
|
||||
- #536260 by Agileware: Make "Add more values" button text themeable.
|
||||
|
||||
Bugfixes:
|
||||
- Fix Use of undefined constant _add_new_group.
|
||||
- Fix undefined index '#depth'.
|
||||
- Fix warning: Creating default object from empty value in template_preprocess_content_display_overview_form() (line 134 of ..theme.inc).
|
||||
- #1063338 by DeFr: Fix undefined indexes for FIELD_NAME_rendered and others.
|
||||
- Fix undefined group name index in fieldgroup_nodeapi.
|
||||
- #1053566 by DamienMcKenna: Fix undefined index errors in _fieldgroup_get_tree().
|
||||
- #1081072 Must be able to save empty, non-required, multigroup, even if it contains required fields.
|
||||
- #522564 Remove empty groups even if not marked 'remove'.
|
||||
- Multigroup validation was defaulting to 'required' when created, should default to 'not required'.
|
||||
- #1092044 Make sure all multigroup formats are preserved, even if not visible on the current tab.
|
||||
|
||||
CCK 6.x-3.0-alpha1
|
||||
==================
|
||||
|
||||
Features:
|
||||
- #1049790 Add tests for fieldgroup.
|
||||
- #849420 by Roberto Gerola, rconstantine, thekevinday, ericduran, KarenS Add ability to nest fieldgroups within other fieldgroups.
|
||||
- #1008184 by merlinofchaos, bojanz, dereine, yched: Adapt to Views 3 "semantic views" feature (backwards compatible with Views 2)
|
||||
- #932680 by Dave Reid: Token integration : allow using of Token API's new $options
|
||||
- #863226 by KarenS, make sure we have a function that will return inactive instances when other instances of the same field are still active.
|
||||
- #692822 by Dave Reid, add authoring info and publishing options to CCK extra fields.
|
||||
- #428650 Conditional cache/menu rebuild for content CRUD methods.
|
||||
- #334945 Save default values when field is hidden because of access permissions.
|
||||
- #196421 Deleting unwanted multiple values / multiple values delta issues.
|
||||
- #119102 Combo field - group different fields into one.
|
||||
- #505278 Panels 3 and multiple node type fields.
|
||||
- #495582 Reviewed Panels 3 integration (prep work for combo / multigroups).
|
||||
Implementation of fieldgroup_view_group() that can be used to render field groups.
|
||||
- #417122 by quicksketch: allow drupal_alter on field and widget settings.
|
||||
- #514452 Add new argument $node to content_access() to enhance the context for hook_field_access().
|
||||
- #523072 by merlinofchaos - Have nodereference relationships limit CCK field availability as well.
|
||||
- #519870 by joachim - Add a note to say offset starts from 0 in grouping options for views handler for multiple values fields.
|
||||
- #231453 Allow fields index their columns. Implemented for reference value column in node and user reference fields. Needs update.php.
|
||||
- #536730 Enhance cells in multiple column tables with CSS classes related to the fields they contain.
|
||||
- #521002 by mh86 - Support for optgroups in allowed values for select elements.
|
||||
- Render field descriptions as cell titles when multigroup edit mode is configured with multiple column option.
|
||||
- #244896 by stella, canaryMason - Add incremental classes for multiple value fields in views.
|
||||
- #416154 Preparation for Content Multigroup integration with Views.
|
||||
- #416154 by coltrane, skybow - Synchronized deltas Views integration: Filter on equal deltas in multigroups.
|
||||
- #227129 by igor.ro - Expose "delta" column in multiple value fields to Views.
|
||||
- #531662 by neochief - i18n support. Allow external modules to translate field labels, descriptions and allowed values list as typed in the field settings form.
|
||||
- #531662 i18n support for fieldgroups.
|
||||
- #558420 Accept trimmed titles in nodereference autocomplete validation to prevent title mismatch errors when title ends with space.
|
||||
- #580156 Wrap multigroups with unique CSS classes in node view.
|
||||
- #544542 Allow subgroup fieldsets in a multigroup to be collapsible.
|
||||
- #596428 by NancyDru - Allow external modules alter the content type list.
|
||||
- #670344 by dagmar: Make CCK compatible with both, views 2 and views 3.
|
||||
|
||||
Bugfixes:
|
||||
- Multigroups were defaulting to 'required' when created, should default to 'not required'.
|
||||
- #766734 Restructure multigroup field layout to be consistent with other fieldgroups, and use
|
||||
content_get_nested_elements() to grab the right values no matter how the fields are structured.
|
||||
- #739490 by foripepe: Token integration - fix notices during token generation
|
||||
- #986612 by Dave Reid: Token integration - fix variable name clash (harmless in normal cases)
|
||||
- #435520 by yched, sun: Fix text fields rendered as 'n/a' in some cases
|
||||
- #728472 by Darren Oh : Ensure the module's preprocess functions run first
|
||||
- #894880 by yched: fix notices in check_plain() when rendering empty 'plain text' values
|
||||
- #705512 by cha0s, roderick: 'add more' button - fix PHP5.3 compatibility
|
||||
- #736440 by yched, dhthwy: fix memory leaks on long running migration scripts (e.g. migrate.module)
|
||||
- #887742 by yched: fix notices in _content_get_formatter() in some Views
|
||||
- #470470 by neilnz, use iLIKE for postgres selects.
|
||||
- #769592 by vkareh, add default values to nodeapi.
|
||||
- #714762 by Robbert, make diff module integration PHP5 compliant.
|
||||
- Add sanitization to nodereference formatters.
|
||||
- #482774 Update breaks when CCK is disabled.
|
||||
- #479994 by quicksketch: fix "add more' button with devel.module's query logging (multigroup).
|
||||
- #499696 by DeFr - Noderefernce / Userreference: fix Views mode when the view has exposed filters.
|
||||
- #498924 #multiple FAPI attribute is used for a radios and checkboxes in content export forms.
|
||||
- #409144 Review extra elements for node edit form provided by core modules.
|
||||
- #361473 CCK fieldgroup panels doesn't respect CCK field privacy settings.
|
||||
- #515984 Multiple field delta ORDER BY incorrect.
|
||||
- #414298 by Michelle, merlinofchaos - Follow up to remove fieldgroup.panels.inc (it was moved to panels/content_types).
|
||||
- #522112 by hefox, prevent malformed condition for vid IN () in views handler for multiple values fields.
|
||||
- #505278 by Michelle, merlinofchaos - Provide backward compatibility with previous method to build Panels 3 subtype names for fields.
|
||||
- #523864 Minor coding style issues in Panels 3 relationships implementations.
|
||||
- #83787 Fix PHP warning: array_merge(): Argument #1 is not an array in content_multigroup.node_form.inc on line 432.
|
||||
- #481568 by merlinofchaos - Empty property error when attempting to save a user reference in Panels.
|
||||
- #510396 by yched - Use field/type definition to render fields in views.
|
||||
- #526500 Fix maximum number of deltas in multigroups with explicit number of repeats defined.
|
||||
- #393020 by auth - Fieldgroup data is lost when importing to module provided content type with group info for existing fields.
|
||||
- #538872 Diff does not respect field permissions.
|
||||
- #522558 Date field jumps delta when date field is emptied or fieldset is deleted.
|
||||
- #416134 Userreference, impossible to filter allowed values by blocked users. Requires update.php.
|
||||
- Minor fix in multigroup. Remove the check for module_exists('fieldgroup'), which is something implicit.
|
||||
- Minor fix in multigroup. Remove unused argument $form_id from invocation to worker functions in hook_form_alter().
|
||||
- #545942 warning: array_filter() [function.array-filter]: The first argument should be an array in userreference_update_6002().
|
||||
- #521002 Fix validation errors when using optgroups in allowed values for select elements.
|
||||
- #550252 by GuyPaddock - content_db_index_exists produces SQL errors when creating node reference fields for MySQL 4 (related to #231453).
|
||||
- #551280 by xurizaemon - Typo fix for "this field cannot hold more that 3 values" error message.
|
||||
- #558744 by chellomere - Fix one of the swedish translation strings to be correct, and much clearer.
|
||||
- #562260 by przadka - content_db_index_exists() has wrong syntax for PostgreSQL.
|
||||
- #567168 by jcmarco - Checkbox required not defined for on/off widgets.
|
||||
- #568430 by Jody Lynn - Bad @see in content-field.tpl.php.
|
||||
- #572672 by Jan van Diepen - Remove redundant (and bad) inclusion of node/content_types.inc in content_copy_import_form_submit().
|
||||
- #585048 Setting "All users" in "User status that can be referenced" option reverts to "Blocked users".
|
||||
- #589306 warning: Invalid argument supplied for foreach() in includes/panels/content_types/content_field.inc on line 166.
|
||||
- #551188 "Add another item" for FileField widgets causes Invalid argument supplied for foreach() in content.node_form.inc on line 456.
|
||||
- #605152 by pokurek - Missing number formatter fr_2.
|
||||
- #618910 Multigroup filter fails when using relationship.
|
||||
- #538458 Do not allow to change the widget type for fields in multigroups when the change is not compatible.
|
||||
- #604830 by mattyoung - 32 characters limit on field and group identifiers in "Manage fields" screen.
|
||||
- #464030 by eojthebrave - Typo in content_copy.module help.
|
||||
- #577590 Add a visual indication to the fieldgroup title if the multigroup is required.
|
||||
- #577590 Prevent validation errors when multigroup is not required and no subgroup of fields if filled in.
|
||||
- #577580 Multigroup fields with empty values loose their ordering when saved via node_save.
|
||||
- #614292 by DeFr - Fix CCK Reference fields based on views broken by recent change in views_plugin_style Views 2.7 (#502348).
|
||||
- #625768 CCK 6.x-2.6, got fatal error on update.php while running userreference_update_6002().
|
||||
- #640488 warning: max() [function.max]: Array must contain at least one element in content.module on line 1044.
|
||||
- #649106 by thekevinday: Fix content_copy_form_alter(), where $form_state argument is not passed by reference.
|
||||
- #669800 Do not enforce required attribute for multiple value fields the current user is not allowed to edit.
|
||||
- Fix validation of required fields and multigroups.
|
||||
- SA-CONTRIB-2010-088 follow up fix for nodereference_autocomplete_access() and content_access().
|
||||
|
||||
Changes:
|
||||
- #421116 Move content.js to js/content.admin.js for consistency with location of new js files.
|
|
@ -1,5 +0,0 @@
|
|||
|
||||
DEVELOPER DOCUMENTATION
|
||||
UPDATING FROM 5.x TO 6.x
|
||||
|
||||
See http://drupal.org/node/191796 for a guide to updating field modules.
|
|
@ -1,339 +0,0 @@
|
|||
GNU GENERAL PUBLIC LICENSE
|
||||
Version 2, June 1991
|
||||
|
||||
Copyright (C) 1989, 1991 Free Software Foundation, Inc.,
|
||||
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
|
||||
Everyone is permitted to copy and distribute verbatim copies
|
||||
of this license document, but changing it is not allowed.
|
||||
|
||||
Preamble
|
||||
|
||||
The licenses for most software are designed to take away your
|
||||
freedom to share and change it. By contrast, the GNU General Public
|
||||
License is intended to guarantee your freedom to share and change free
|
||||
software--to make sure the software is free for all its users. This
|
||||
General Public License applies to most of the Free Software
|
||||
Foundation's software and to any other program whose authors commit to
|
||||
using it. (Some other Free Software Foundation software is covered by
|
||||
the GNU Lesser General Public License instead.) You can apply it to
|
||||
your programs, too.
|
||||
|
||||
When we speak of free software, we are referring to freedom, not
|
||||
price. Our General Public Licenses are designed to make sure that you
|
||||
have the freedom to distribute copies of free software (and charge for
|
||||
this service if you wish), that you receive source code or can get it
|
||||
if you want it, that you can change the software or use pieces of it
|
||||
in new free programs; and that you know you can do these things.
|
||||
|
||||
To protect your rights, we need to make restrictions that forbid
|
||||
anyone to deny you these rights or to ask you to surrender the rights.
|
||||
These restrictions translate to certain responsibilities for you if you
|
||||
distribute copies of the software, or if you modify it.
|
||||
|
||||
For example, if you distribute copies of such a program, whether
|
||||
gratis or for a fee, you must give the recipients all the rights that
|
||||
you have. You must make sure that they, too, receive or can get the
|
||||
source code. And you must show them these terms so they know their
|
||||
rights.
|
||||
|
||||
We protect your rights with two steps: (1) copyright the software, and
|
||||
(2) offer you this license which gives you legal permission to copy,
|
||||
distribute and/or modify the software.
|
||||
|
||||
Also, for each author's protection and ours, we want to make certain
|
||||
that everyone understands that there is no warranty for this free
|
||||
software. If the software is modified by someone else and passed on, we
|
||||
want its recipients to know that what they have is not the original, so
|
||||
that any problems introduced by others will not reflect on the original
|
||||
authors' reputations.
|
||||
|
||||
Finally, any free program is threatened constantly by software
|
||||
patents. We wish to avoid the danger that redistributors of a free
|
||||
program will individually obtain patent licenses, in effect making the
|
||||
program proprietary. To prevent this, we have made it clear that any
|
||||
patent must be licensed for everyone's free use or not licensed at all.
|
||||
|
||||
The precise terms and conditions for copying, distribution and
|
||||
modification follow.
|
||||
|
||||
GNU GENERAL PUBLIC LICENSE
|
||||
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
|
||||
|
||||
0. This License applies to any program or other work which contains
|
||||
a notice placed by the copyright holder saying it may be distributed
|
||||
under the terms of this General Public License. The "Program", below,
|
||||
refers to any such program or work, and a "work based on the Program"
|
||||
means either the Program or any derivative work under copyright law:
|
||||
that is to say, a work containing the Program or a portion of it,
|
||||
either verbatim or with modifications and/or translated into another
|
||||
language. (Hereinafter, translation is included without limitation in
|
||||
the term "modification".) Each licensee is addressed as "you".
|
||||
|
||||
Activities other than copying, distribution and modification are not
|
||||
covered by this License; they are outside its scope. The act of
|
||||
running the Program is not restricted, and the output from the Program
|
||||
is covered only if its contents constitute a work based on the
|
||||
Program (independent of having been made by running the Program).
|
||||
Whether that is true depends on what the Program does.
|
||||
|
||||
1. You may copy and distribute verbatim copies of the Program's
|
||||
source code as you receive it, in any medium, provided that you
|
||||
conspicuously and appropriately publish on each copy an appropriate
|
||||
copyright notice and disclaimer of warranty; keep intact all the
|
||||
notices that refer to this License and to the absence of any warranty;
|
||||
and give any other recipients of the Program a copy of this License
|
||||
along with the Program.
|
||||
|
||||
You may charge a fee for the physical act of transferring a copy, and
|
||||
you may at your option offer warranty protection in exchange for a fee.
|
||||
|
||||
2. You may modify your copy or copies of the Program or any portion
|
||||
of it, thus forming a work based on the Program, and copy and
|
||||
distribute such modifications or work under the terms of Section 1
|
||||
above, provided that you also meet all of these conditions:
|
||||
|
||||
a) You must cause the modified files to carry prominent notices
|
||||
stating that you changed the files and the date of any change.
|
||||
|
||||
b) You must cause any work that you distribute or publish, that in
|
||||
whole or in part contains or is derived from the Program or any
|
||||
part thereof, to be licensed as a whole at no charge to all third
|
||||
parties under the terms of this License.
|
||||
|
||||
c) If the modified program normally reads commands interactively
|
||||
when run, you must cause it, when started running for such
|
||||
interactive use in the most ordinary way, to print or display an
|
||||
announcement including an appropriate copyright notice and a
|
||||
notice that there is no warranty (or else, saying that you provide
|
||||
a warranty) and that users may redistribute the program under
|
||||
these conditions, and telling the user how to view a copy of this
|
||||
License. (Exception: if the Program itself is interactive but
|
||||
does not normally print such an announcement, your work based on
|
||||
the Program is not required to print an announcement.)
|
||||
|
||||
These requirements apply to the modified work as a whole. If
|
||||
identifiable sections of that work are not derived from the Program,
|
||||
and can be reasonably considered independent and separate works in
|
||||
themselves, then this License, and its terms, do not apply to those
|
||||
sections when you distribute them as separate works. But when you
|
||||
distribute the same sections as part of a whole which is a work based
|
||||
on the Program, the distribution of the whole must be on the terms of
|
||||
this License, whose permissions for other licensees extend to the
|
||||
entire whole, and thus to each and every part regardless of who wrote it.
|
||||
|
||||
Thus, it is not the intent of this section to claim rights or contest
|
||||
your rights to work written entirely by you; rather, the intent is to
|
||||
exercise the right to control the distribution of derivative or
|
||||
collective works based on the Program.
|
||||
|
||||
In addition, mere aggregation of another work not based on the Program
|
||||
with the Program (or with a work based on the Program) on a volume of
|
||||
a storage or distribution medium does not bring the other work under
|
||||
the scope of this License.
|
||||
|
||||
3. You may copy and distribute the Program (or a work based on it,
|
||||
under Section 2) in object code or executable form under the terms of
|
||||
Sections 1 and 2 above provided that you also do one of the following:
|
||||
|
||||
a) Accompany it with the complete corresponding machine-readable
|
||||
source code, which must be distributed under the terms of Sections
|
||||
1 and 2 above on a medium customarily used for software interchange; or,
|
||||
|
||||
b) Accompany it with a written offer, valid for at least three
|
||||
years, to give any third party, for a charge no more than your
|
||||
cost of physically performing source distribution, a complete
|
||||
machine-readable copy of the corresponding source code, to be
|
||||
distributed under the terms of Sections 1 and 2 above on a medium
|
||||
customarily used for software interchange; or,
|
||||
|
||||
c) Accompany it with the information you received as to the offer
|
||||
to distribute corresponding source code. (This alternative is
|
||||
allowed only for noncommercial distribution and only if you
|
||||
received the program in object code or executable form with such
|
||||
an offer, in accord with Subsection b above.)
|
||||
|
||||
The source code for a work means the preferred form of the work for
|
||||
making modifications to it. For an executable work, complete source
|
||||
code means all the source code for all modules it contains, plus any
|
||||
associated interface definition files, plus the scripts used to
|
||||
control compilation and installation of the executable. However, as a
|
||||
special exception, the source code distributed need not include
|
||||
anything that is normally distributed (in either source or binary
|
||||
form) with the major components (compiler, kernel, and so on) of the
|
||||
operating system on which the executable runs, unless that component
|
||||
itself accompanies the executable.
|
||||
|
||||
If distribution of executable or object code is made by offering
|
||||
access to copy from a designated place, then offering equivalent
|
||||
access to copy the source code from the same place counts as
|
||||
distribution of the source code, even though third parties are not
|
||||
compelled to copy the source along with the object code.
|
||||
|
||||
4. You may not copy, modify, sublicense, or distribute the Program
|
||||
except as expressly provided under this License. Any attempt
|
||||
otherwise to copy, modify, sublicense or distribute the Program is
|
||||
void, and will automatically terminate your rights under this License.
|
||||
However, parties who have received copies, or rights, from you under
|
||||
this License will not have their licenses terminated so long as such
|
||||
parties remain in full compliance.
|
||||
|
||||
5. You are not required to accept this License, since you have not
|
||||
signed it. However, nothing else grants you permission to modify or
|
||||
distribute the Program or its derivative works. These actions are
|
||||
prohibited by law if you do not accept this License. Therefore, by
|
||||
modifying or distributing the Program (or any work based on the
|
||||
Program), you indicate your acceptance of this License to do so, and
|
||||
all its terms and conditions for copying, distributing or modifying
|
||||
the Program or works based on it.
|
||||
|
||||
6. Each time you redistribute the Program (or any work based on the
|
||||
Program), the recipient automatically receives a license from the
|
||||
original licensor to copy, distribute or modify the Program subject to
|
||||
these terms and conditions. You may not impose any further
|
||||
restrictions on the recipients' exercise of the rights granted herein.
|
||||
You are not responsible for enforcing compliance by third parties to
|
||||
this License.
|
||||
|
||||
7. If, as a consequence of a court judgment or allegation of patent
|
||||
infringement or for any other reason (not limited to patent issues),
|
||||
conditions are imposed on you (whether by court order, agreement or
|
||||
otherwise) that contradict the conditions of this License, they do not
|
||||
excuse you from the conditions of this License. If you cannot
|
||||
distribute so as to satisfy simultaneously your obligations under this
|
||||
License and any other pertinent obligations, then as a consequence you
|
||||
may not distribute the Program at all. For example, if a patent
|
||||
license would not permit royalty-free redistribution of the Program by
|
||||
all those who receive copies directly or indirectly through you, then
|
||||
the only way you could satisfy both it and this License would be to
|
||||
refrain entirely from distribution of the Program.
|
||||
|
||||
If any portion of this section is held invalid or unenforceable under
|
||||
any particular circumstance, the balance of the section is intended to
|
||||
apply and the section as a whole is intended to apply in other
|
||||
circumstances.
|
||||
|
||||
It is not the purpose of this section to induce you to infringe any
|
||||
patents or other property right claims or to contest validity of any
|
||||
such claims; this section has the sole purpose of protecting the
|
||||
integrity of the free software distribution system, which is
|
||||
implemented by public license practices. Many people have made
|
||||
generous contributions to the wide range of software distributed
|
||||
through that system in reliance on consistent application of that
|
||||
system; it is up to the author/donor to decide if he or she is willing
|
||||
to distribute software through any other system and a licensee cannot
|
||||
impose that choice.
|
||||
|
||||
This section is intended to make thoroughly clear what is believed to
|
||||
be a consequence of the rest of this License.
|
||||
|
||||
8. If the distribution and/or use of the Program is restricted in
|
||||
certain countries either by patents or by copyrighted interfaces, the
|
||||
original copyright holder who places the Program under this License
|
||||
may add an explicit geographical distribution limitation excluding
|
||||
those countries, so that distribution is permitted only in or among
|
||||
countries not thus excluded. In such case, this License incorporates
|
||||
the limitation as if written in the body of this License.
|
||||
|
||||
9. The Free Software Foundation may publish revised and/or new versions
|
||||
of the General Public License from time to time. Such new versions will
|
||||
be similar in spirit to the present version, but may differ in detail to
|
||||
address new problems or concerns.
|
||||
|
||||
Each version is given a distinguishing version number. If the Program
|
||||
specifies a version number of this License which applies to it and "any
|
||||
later version", you have the option of following the terms and conditions
|
||||
either of that version or of any later version published by the Free
|
||||
Software Foundation. If the Program does not specify a version number of
|
||||
this License, you may choose any version ever published by the Free Software
|
||||
Foundation.
|
||||
|
||||
10. If you wish to incorporate parts of the Program into other free
|
||||
programs whose distribution conditions are different, write to the author
|
||||
to ask for permission. For software which is copyrighted by the Free
|
||||
Software Foundation, write to the Free Software Foundation; we sometimes
|
||||
make exceptions for this. Our decision will be guided by the two goals
|
||||
of preserving the free status of all derivatives of our free software and
|
||||
of promoting the sharing and reuse of software generally.
|
||||
|
||||
NO WARRANTY
|
||||
|
||||
11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
|
||||
FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
|
||||
OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
|
||||
PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
|
||||
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
|
||||
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
|
||||
TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
|
||||
PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
|
||||
REPAIR OR CORRECTION.
|
||||
|
||||
12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
|
||||
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
|
||||
REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
|
||||
INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
|
||||
OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
|
||||
TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
|
||||
YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
|
||||
PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
|
||||
POSSIBILITY OF SUCH DAMAGES.
|
||||
|
||||
END OF TERMS AND CONDITIONS
|
||||
|
||||
How to Apply These Terms to Your New Programs
|
||||
|
||||
If you develop a new program, and you want it to be of the greatest
|
||||
possible use to the public, the best way to achieve this is to make it
|
||||
free software which everyone can redistribute and change under these terms.
|
||||
|
||||
To do so, attach the following notices to the program. It is safest
|
||||
to attach them to the start of each source file to most effectively
|
||||
convey the exclusion of warranty; and each file should have at least
|
||||
the "copyright" line and a pointer to where the full notice is found.
|
||||
|
||||
<one line to give the program's name and a brief idea of what it does.>
|
||||
Copyright (C) <year> <name of author>
|
||||
|
||||
This program is free software; you can redistribute it and/or modify
|
||||
it under the terms of the GNU General Public License as published by
|
||||
the Free Software Foundation; either version 2 of the License, or
|
||||
(at your option) any later version.
|
||||
|
||||
This program is distributed in the hope that it will be useful,
|
||||
but WITHOUT ANY WARRANTY; without even the implied warranty of
|
||||
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
||||
GNU General Public License for more details.
|
||||
|
||||
You should have received a copy of the GNU General Public License along
|
||||
with this program; if not, write to the Free Software Foundation, Inc.,
|
||||
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
|
||||
|
||||
Also add information on how to contact you by electronic and paper mail.
|
||||
|
||||
If the program is interactive, make it output a short notice like this
|
||||
when it starts in an interactive mode:
|
||||
|
||||
Gnomovision version 69, Copyright (C) year name of author
|
||||
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
|
||||
This is free software, and you are welcome to redistribute it
|
||||
under certain conditions; type `show c' for details.
|
||||
|
||||
The hypothetical commands `show w' and `show c' should show the appropriate
|
||||
parts of the General Public License. Of course, the commands you use may
|
||||
be called something other than `show w' and `show c'; they could even be
|
||||
mouse-clicks or menu items--whatever suits your program.
|
||||
|
||||
You should also get your employer (if you work as a programmer) or your
|
||||
school, if any, to sign a "copyright disclaimer" for the program, if
|
||||
necessary. Here is a sample; alter the names:
|
||||
|
||||
Yoyodyne, Inc., hereby disclaims all copyright interest in the program
|
||||
`Gnomovision' (which makes passes at compilers) written by James Hacker.
|
||||
|
||||
<signature of Ty Coon>, 1 April 1989
|
||||
Ty Coon, President of Vice
|
||||
|
||||
This General Public License does not permit incorporating your program into
|
||||
proprietary programs. If your program is a subroutine library, you may
|
||||
consider it more useful to permit linking proprietary applications with the
|
||||
library. If this is what you want to do, use the GNU Lesser General
|
||||
Public License instead of this License.
|
|
@ -1,86 +0,0 @@
|
|||
|
||||
================================================================
|
||||
UPDATING FROM VERSION 4.7 to 6.x
|
||||
================================================================
|
||||
|
||||
THERE IS NO DIRECT UPGRADE PATH FROM 4.7 TO 6.x!! FIRST UPGRADE
|
||||
YOUR DATABASE FROM 4.7 TO THE LATEST 5.x VERSION, THEN UPGRADE
|
||||
TO 6.x.
|
||||
|
||||
ALWAYS BACKUP YOUR DATABASE BEFORE UPGRADING!
|
||||
|
||||
1) While 4.7 is still installed, upload the latest 4.7 version of
|
||||
all the CCK files, go to update.php, and run all possible
|
||||
updates for the Content module and all field modules.
|
||||
|
||||
2) Install Drupal version 5. Once it is running, upload and install
|
||||
the latest 5.x versions of all CCK modules, go to update.php and
|
||||
run all possible updates.
|
||||
|
||||
Jump to the instructions for updating from version 5.x to 6.x.
|
||||
|
||||
================================================================
|
||||
UPDATING FROM VERSION 5.x to 6.x
|
||||
================================================================
|
||||
|
||||
YOU MUST RUN ALL POSSIBLE UPDATES TO YOUR DATABASE IN 5.x USING
|
||||
THE LATEST 5.x CODE, BEFORE UPGRADING FROM 5.x to 6.x.
|
||||
|
||||
ALWAYS BACKUP YOUR DATABASE BEFORE UPGRADING!
|
||||
|
||||
1) Before upgrading to 6.x, upload the latest 5.x versions of all
|
||||
CCK modules, go to update.php and run all possible updates.
|
||||
|
||||
2) Disable all CCK modules and remove them from the modules folder
|
||||
before upgrading.
|
||||
|
||||
3) Install Drupal version 6. Leave all contributed modules out of
|
||||
the modules folder until core modules are up and running.
|
||||
Set your administration theme to a core theme like Garland until
|
||||
everything has been updated to help ensure you don't encounter
|
||||
theme-related problems accessing the administration area.
|
||||
|
||||
4) Once core is running, upload and install the latest 6.x versions
|
||||
of ONLY CCK CORE FILES (the ones in the tarball on the CCK
|
||||
project page). Enable them, then go to update.php and run all
|
||||
possible updates. DO NOT add any other CCK modules to the
|
||||
modules folder until the core CCK files are updated and working
|
||||
correctly.
|
||||
|
||||
5) After updating CCK core modules, you may get messages saying that
|
||||
some updates failed and that you need to run update.php again.
|
||||
If you get messages like that, keep re-running update.php until
|
||||
you get no more messages.
|
||||
|
||||
6) Once the core CCK modules are updated and working correctly,
|
||||
add other CCK modules to the modules folder, enable them,
|
||||
and run update.php. For best results, do this one module at a
|
||||
time so you can tell immediately if any of them create problems
|
||||
without letting those problems interfere with other updates.
|
||||
|
||||
|
||||
Your database should now be ready to run in CCK version 6.x
|
||||
|
||||
================================================================
|
||||
|
||||
The 4.7 to 5.x steps are necessary because of significant changes
|
||||
in the database structure between the 4.7 and 6.x versions. These changes
|
||||
make it extremely difficult to create an automatic upgrade path that
|
||||
will work reliably in every possible situation.
|
||||
|
||||
The extra steps in the 5.x to 6.x upgrade are because all modules
|
||||
in the modules folder are automatically updated in Drupal 6, even if they
|
||||
are not enabled. That means that modules that rely on core CCK may try
|
||||
to run their updates even if core CCK is not enabled, and contributed
|
||||
CCK modules that have broken updates will have their broken updates
|
||||
run even if they are not enabled.
|
||||
|
||||
A number of updates are dependent on other updates and won't work
|
||||
until previous updates are finished or specific modules are enabled,
|
||||
so you may get messages that other modules need to be enabled or that
|
||||
update.php needs to be re-run, and you need to follow those instructions
|
||||
until all the updates complete.
|
||||
|
||||
Taking extra time during the upgrade by leaving modules out of the
|
||||
modules folder altogether until you are ready to enable and update them
|
||||
should reduce or eliminate update problems.
|
Reference in a new issue