3954704dda
There was a conflict between two repeaters that had the same fieldName (data) bound to the same controller. Example: Controller: Events Manages a ReportTemplate model with a custom popup Form widget that uses a grouped repeater with the field name data to define the available "fields" within a ReportTemplate Also manages Report models through a relation controller that uses a Form widget with a regular repeater with the field name data that defines the values of the fields defined by the associated ReportTemplate. Since both repeaters had the field name of "data", but one of them was grouped and the other wasn't, this would cause an issue in Repeater::processExistingItems() where the grouped repeater would attempt to process the ungrouped repeater's data which would then fail. This issue could easily cause many other vastly more confusing and difficult to detect issues in cases where multiple repeaters with the same field name AND the same mode (grouped vs regular) existed on the same page under different contexts. The simple solution is just to ensure that the indexInputName and groupInputName are both taking the repeater's alias into account when being generated to ensure that everything stays unique like it should. |
||
|---|---|---|
| .github | ||
| bootstrap | ||
| config | ||
| modules | ||
| plugins/october/demo | ||
| storage | ||
| tests | ||
| themes/demo | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .htaccess | ||
| .travis.yml | ||
| CHANGELOG.md | ||
| CODE_OF_CONDUCT.md | ||
| LICENSE | ||
| README.md | ||
| artisan | ||
| composer.json | ||
| index.php | ||
| phpunit.xml | ||
| server.php | ||
README.md
October is a Content Management System (CMS) and web platform whose sole purpose is to make your development workflow simple again. It was born out of frustration with existing systems. We feel building websites has become a convoluted and confusing process that leaves developers unsatisfied. We want to turn you around to the simpler side and get back to basics.
October's mission is to show the world that web development is not rocket science.
Learning October
The best place to learn October is by reading the documentation or following some tutorials.
You may also watch these introductory videos for beginners and advanced users.
Installing October
Instructions on how to install October can be found at the installation guide.
Quick start installation
For advanced users, run this in your terminal to install October from command line:
php -r "eval('?>'.file_get_contents('https://octobercms.com/api/installer'));"
If you plan on using a database, run this command:
php artisan october:install
Development Team
October was created by Alexey Bobkov and Samuel Georges, who (along with Luke Towers) continue to develop the platform.
Foundation library
The CMS uses Laravel as a foundation PHP framework.
Contact
You can communicate with us using the following mediums:
- Follow us on Twitter for announcements and updates.
- Follow us on Facebook for announcements and updates.
- Join us on IRC to chat with us.
- Join us on Slack to chat with us.
License
The OctoberCMS platform is open-sourced software licensed under the MIT license.
Contributing
Before sending a Pull Request, be sure to review the Contributing Guidelines first.
Coding standards
Please follow the following guides and code standards: