Timeline for How to debug an empty Bootstrap error generated by non-empty Tags field in a custom component?
Current License: CC BY-SA 4.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Sep 15, 2018 at 13:06 | history | suggested | mickmackusa | CC BY-SA 4.0 |
added commented advice to question
|
| Sep 14, 2018 at 8:22 | comment | added | Sharky | Update files are incremental. They must include only changes introduced with their versions. For example, if you add a new content type in 1.0.1, you need to create a 1.0.1 update file containing the query and also update the install/uninstall files. If you don't make any database changes in 1.0.2, you don't even need a 1.0.2 update file. But if you do, the update file must contain only changes introduced in 1.0.2. Changes from 1.0.1 will be applied automatically from 1.0.1 file. | |
| Sep 14, 2018 at 7:53 | comment | added | mickmackusa |
Right. I've nulled the id column values. I am solely concerned with subsequent installs where I have additional .sql files in the updates/mysql folder. If I duplicate the two-row INSERT query, I'll be generating redundant rows.
|
|
| Sep 14, 2018 at 7:47 | comment | added | Sharky | If this is the initial release of your component (e.g. 1.0.0), you don't need an update file. Add the queries to install file only. Remember to remove ID columns/values from the query - these must be auto incremented. Going forward (1.0.1 and beyond) any SQL changes will need to be made in both install and update files. | |
| Sep 14, 2018 at 5:58 | comment | added | mickmackusa |
Please forgive my question extension... I am now trying to package up my component and I need to write the above two rows into sql/updates/mysql/1.0.0.sql.sql and sql/updates/install.mysql.utf8.sql. However, the type_title column in #__content_types is not UNIQUE by default, so I can't do a INSERT IGNORE. Do I need to something more complicated like a post_flight script to check and conditionally insert the two rows? Inspiration from Prof. Babker: joomla.stackexchange.com/a/708/12352
|
|
| Sep 12, 2018 at 23:46 | comment | added | mickmackusa | ...nevermind about the version note. Everything is working as intended, I misunderstood the functionality. | |
| Sep 12, 2018 at 20:52 | comment | added | mickmackusa | I did read that documentation page, but I mustn't have looked carefully enough about what I was doing. Thanks for the extra pair of eyes. The tags are now saving. Any ideas as to why I can't get version notes to save on any of my components? Or shall I post a new question? | |
| Sep 12, 2018 at 20:51 | review | Suggested edits | |||
| S Sep 15, 2018 at 13:06 | |||||
| Sep 12, 2018 at 20:40 | vote | accept | mickmackusa | ||
| Sep 12, 2018 at 12:29 | comment | added | Sharky |
You added a row for com_picture.category but not for com_picture.picture.
|
|
| Sep 12, 2018 at 10:21 | comment | added | mickmackusa | I didn't want to bloat my question any farther with a bunch of sql rows that I manufactured, but I might need to add these details for absolute clarity. | |
| Sep 12, 2018 at 9:50 | comment | added | mickmackusa | I have updated my question to include the row that I already inserted into the table. | |
| Sep 12, 2018 at 9:00 | history | answered | Sharky | CC BY-SA 4.0 |