Thread

i’ve recently upgraded a client from 1.6.8 to 2.1.2

I’m using smartdown to format the URL. the client used markdown and smartdown is the 2.0 solution.

However, I’ve noticed something. When i choose the default formatting in the custom fields for this, it’s not storing those settings. it puts a null value in the field. But if I change it, and then tic to the box to update all existing channel entries, it does it correctly.

The issue is only when posting new entries. i can successfully convert all existing entries using the utility listed above, but new entries get no vaule in the db for the formatting.

I thought it might be a smartdown issue, but removing the add-on doesn’t resolve the problem.

Second part of this issue, the option is checked to allow overrides, but they do not appear in the publish page. Neither do the formatting buttons if I enable them.

Thanks for any help.

Any suggestions?

Is there something special I need to do to get help on this? getting a bit frustrated.

FYI for a band aid on this, I enumerated the field and set a default value of ‘none’ on formatting. that fixes the problem where EE is not setting the value, but it’s not a fix. I sincerely need help here.

Is there something special I need to do to get help on this?

Not bumping the thread might help. Seriously, we queue threads by last activity in thread. Every time you add to it it goes to the bottom of the queue. I’m taking this one out of order for now.

When i choose the default formatting in the custom fields for this, it’s not storing those settings. it puts a null value in the field. But if I change it, and then tic to the box to update all existing channel entries, it does it correctly.

This is all using the built-in CP, yes? Unless you are on 2.1.3 already an upgrade is urgently suggested. Any other extensions or third-party add-ons?

... but new entries get no vaule in the db for the formatting.

Again, this entry is submitted via the control panel, correct?

ahh ok that makes sense on the queue. I’ll try not to be one of those annoying guys that does that 😊

yes this is all through the CP. i actually didn’t know 2.1.3 was out. 

But I did catch a bug report that addressed this it’s here
Bug 14786

The problem is the work around didnt work, or I’d be good to go. Hopefully, based on that bug, upgrading might resolve it which would be just dandy.

I’ll follow up

Just a follow up, upgrading fixed that problem. So we’re good to go.

Hey JT, glad that you got it sorted with an upgrade.  If you have any other questions, please start a new thread and we’ll help you out!

Thanks. =)