Under Extensions > Plugins, search Fields - Integer
.
Edit this plugin to see fields to set including First, Last, and Step fields.
Go to Content > Fields.
Create a new field.
Select Integer
from the dropdown.
First, Last, and Step fields should be populated with values from the plugin.
First, Last, and Step fields are blank.
RC3
Labels |
Added:
?
|
Updated ticket to more accurately describe the issue.
from my perspective the only issue is that the First, Last and Step fields in the field defintion should say "from plugin or enter a value" and not be blank
Say i understand you now.i am not at my computer anymore but iirc you should to see if the plugin has default values stored in the dB. I suspect not and that is the issue. The install SQL can be updated to fix that if my guess is correct
The plugin has default values, but it seems you have to initialize/save it for it to be in effect.
Which means that the default values are not present in the database on install and are only in the XML. They should be in both
The database actually doesn't matter that much. The default values should be in the XML and in the code where the param is requested.
Title |
|
Category | ⇒ | com_fields |
@bakual maybe you are right and the default values are missing in the code from where the param is requested - I dont know where to look for that. I can say for certain that it resolved by setting the default param in the sql on install - but if you say thats the wrong way then I will wait for your reply as my PR would be wrong
I had a look and the way the params are merged, we can't easily add the default values to the code. So your approach with the database looks indeed better and easier.
OK - I will work on a PR now then
Title |
|
||||||
Status | New | ⇒ | Closed | ||||
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2017-04-19 09:17:03 | ||||
Closed_By | ⇒ | brianteeman |
I can confirm that they are blank BUT if you leave them blank and look at the values in the generated field they match the values set in the plugin - so it does work but there is a UI bug