Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Is this when saving a new field or an existing field?I am not sure if this is correct behavior or not (hoping it is not) When I try to save a "text field" as searchable I am prompted that calculated fields cannot be searchable. However a "text area" is. If I initially save it as a text area that is searchable it saves & I can then change it to a text field and it still says it is searchable..
That shouldn't be an issue anymore. This is fixed by changing the database engine for CB tables to InnoDB. This is not done automatically for upgrade installs so if you upgraded from CB 1.x to 2.0 please be sure to run CB > Tools to check for database changes.Row size too large. The maximum row size for the used table type, not counting BLOBs, is 65535. You have to change some columns to TEXT or BLOBs SQL=ALTER TABLE `tprw5_comprofiler` ADD `cb_song_name149` varchar(255) DEFAULT NULL
I know that in the xml file you can change it from "varchar(255)" to "text" but to make it easy for those whose skills are a bit limited can there be a tool that does it for the field types? That way people are not constantly asking how to fix this error or screwing up their site because they make a goofy mistake and then cant figure out what they did wrong?
That's not really possible at this time due to the way field names save. Ideally we'd like for any field except unique, calculated, or system to allow for name change, but currently that's not possible without causing issues for various plugins. Once a field saves it locks the name, there's no inbetween state so it can't leave the name editable. I've created a feature ticket to look into allowing name editing for some fields.When we go to create a new field would it be possible to have a "save as copy" that saves the settings of the field but does not automatically give it the name or title? This would enable us to maintain a good naming scheme. Currently the listed copy feature makes it difficult to maintain a numerical sequence to replicated fields.
Please Log in or Create an account to join the conversation.
krileon wrote:
Is this when saving a new field or an existing field?I am not sure if this is correct behavior or not (hoping it is not) When I try to save a "text field" as searchable I am prompted that calculated fields cannot be searchable. However a "text area" is. If I initially save it as a text area that is searchable it saves & I can then change it to a text field and it still says it is searchable..
Saving a new field.
That shouldn't be an issue anymore. This is fixed by changing the database engine for CB tables to InnoDB. This is not done automatically for upgrade installs so if you upgraded from CB 1.x to 2.0 please be sure to run CB > Tools to check for database changes.Row size too large. The maximum row size for the used table type, not counting BLOBs, is 65535. You have to change some columns to TEXT or BLOBs SQL=ALTER TABLE `tprw5_comprofiler` ADD `cb_song_name149` varchar(255) DEFAULT NULL
I know that in the xml file you can change it from "varchar(255)" to "text" but to make it easy for those whose skills are a bit limited can there be a tool that does it for the field types? That way people are not constantly asking how to fix this error or screwing up their site because they make a goofy mistake and then cant figure out what they did wrong?
This was a fresh install
That's not really possible at this time due to the way field names save. Ideally we'd like for any field except unique, calculated, or system to allow for name change, but currently that's not possible without causing issues for various plugins. Once a field saves it locks the name, there's no inbetween state so it can't leave the name editable. I've created a feature ticket to look into allowing name editing for some fields.When we go to create a new field would it be possible to have a "save as copy" that saves the settings of the field but does not automatically give it the name or title? This would enable us to maintain a good naming scheme. Currently the listed copy feature makes it difficult to maintain a numerical sequence to replicated fields.
forge.joomlapolis.com/issues/4565
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.