I’m still subscribed to this thread, but any future posts with be greeted with a polite request to re-post on the official support site.
—-
Hello all,
As Ryan Masuga blogged a few weeks back, creating weblog fields with custom formatting in ExpressionEngine is a pain.
Create the field, save it, open it for editing, click “Edit List” to update the available formatting options, dismiss the warning dialogue, update the formatting selections, save the form, select the required formatting from the new list of available options, save the field, weep, repeat.
SL Field Formatting is here to save you from the tedium, without the need to hack your core files.
Easily specify the default list of formatting options that will appear for all new weblog fields, and seamlessly update all of your existing fields, whilst respecting their currently selected formatting.
So I successfully installed it on another site and tried to convert a standard field with formatting ‘none’ into a nGen file-field which contained uploaded images via the EE upload (so in this format {fildir_1}image.jpg) and this is the error I get:
Warning: exif_imagetype(/.../..../.../maizebreak.com/images/uploads/{filedir_1}chuck-norris-inline.jpg) [function.exif-imagetype]: failed to open stream: No such file or directory in /.../..../.../maizebreak.com/.../extensions/fieldtypes/ngen_file_field/ft.ngen_file_field.php on line 742
Is this not possible? If so, what type of “field-type to field-type” conversions does it support? Thanks!
So I successfully installed it on another site and tried to convert a standard field with formatting ‘none’ into a nGen file-field which contained uploaded images via the EE upload (so in this format {fildir_1}image.jpg) and this is the error I get:
I’m confused as to what you’re attempting to do here.
Just to clarify, the extension is specifically designed to make it easy to set the default formatting options that are available when you create a new (usually text area) custom weblog field.
The error looks like there’s a problem with your file upload location, which is unlikely to be related to this extension (in fact, I can’t think how it could be).
Ok, I was under the impression that I can take any type of already created field and change the “field type”, as long as it was similar and it would keep the existing data in that field and also update the field type.
Ok, I was under the impression that I can take any type of already created field and change the “field type”, as long as it was similar and it would keep the existing data in that field and also update the field type.
You’re confusing field types with field formatting. This extension is concerned solely with the latter (see attached explanatory screenshot).
Gotcha! Kinda came to that same conclusion after a bit of brain power…which I seriously lack sometimes.
I noticed that you can select plugins as formatting options. If I choose a plugin, does it pseudo wrap the field and format it based on the plugin? If so, what about the plugin’s parameters? How does that work?
I noticed that you can select plugins as formatting options. If I choose a plugin, does it pseudo wrap the field and format it based on the plugin? If so, what about the plugin’s parameters? How does that work?
For reasons best known to EllisLab, every plugin is automatically made available as a formatting option, regardless of whether it makes sense to do so (Magpie, XML Encode, Randomizer, eh?).
Basically it’s up to you to exercise some common sense, and choose a plugin that will actually do something sensible with the text you enter.
For example, if you choose the “Markdown” plugin for a field’s formatting, you can then happily use Markdown in the text area, and EE takes care of the conversion to HTML behind the scenes. No need to add extra {exp:markdown} tags (or the like) to your templates.
After a bit more research, I think my problem was unrelated to this plugin (just pure coincidence that I noticed the problem right after installing this plug.)
After a bit more research, I think my problem was unrelated to this plugin (just pure coincidence that I noticed the problem right after installing this plug.)
No problem Micky, thanks for letting me know. Glad you’re liking the addon.
Ran into a problem where I couldn’t add a custom field. Through the tedious process of elimination, turning off & on groups of extensions, I can now add a field, but the settings page for Field Formatting gives me a white screen.
I downloaded and replaced the files, but still no go.
