Extension: MD Dulee Noted. A non-editable note field type to add instructions to weblogs

Nine times out of ten this is an extension conflict.

Ok, I will test. Thanks much.

Dulee Noted (Now MD Dulee Noted) has been updated to 1.2.0.

• MSM aware
• No more reliance or need for jQuery
• Compatible with LG Addon Updater extension to detect new updates
• Uses EE’s Control Panel box style
• Set the field formatting type! (You’re viewing Xhtml in the attached pic)

You can download it from the MD Dulee Noted Page.

Big thanks to Leevi Graham of Newism for his suggestions and tweaks to the previous version that helped make this version much better.

I’m running into some issues with 1.2.0 where the settings aren’t being read. Deron Sizemore also pointed out an error on Twitter this morning:

I keep getting Undefined index: enable in /web/ksba.org/system/extensions/ext.md_dulee_noted.php on line 364 when I enable it

Line 364 is this:

if($this->settings['enable'] == 'y')

which, in English, is just saying if that if this extension is enabled for this site, carry on. I just got the same error myself installing this on a new site this morning. I checked directly in the database and the settings are in there, but for some reason, the extesnion is not seeing whether or not it is enabled or not.

I’m looking into this now. Not the way I wanted to spend my morning, but you gotta do what you gotta do, and this sort of problem drives me crazy. If any other PHP/entension writing people care to take a look - please do.

ADD: Deron, what version and build of EE did you try this on?

Just installed the newest version and am receiving this message when I go to the “add new custom field” page:

Notice: Undefined index: enable in /web/ksba.org/system/extensions/ext.md_dulee_noted.php on line 364

I was using the previous version of Dulee Noted with no issues. I disabled the old version and completely removed it from my server before installing the new version. Once installed I get the notice above and the new “dulee noted” field type never pops up in the drop down list when creating a new field.

Other extensions I have installed are Textile Editor Helper, LG Site Name, and Tab Forward.

Running EE version 1.6.4 Build: 20080710

Let me know if you need any additional info.

Thanks

Well, if you read all my ranting tweets from this morning, you know this issue almost brought me to introduce Mr. Fist to Mr. Wall 😊 I have no clue why it isn’t reading the settings. I have this working perfectly on a local install, but like you, I installed this on a site this morning and got the exact same errors.

For now I may have to pull the MSM out - but I ran into a further problem when I tried commenting all that MSM stuff out…I got an error on “$this->settings[‘css’]”, which means it basically cannot read the settings at all - and there are only three basic settings: enable, css, and check for updates.

This is probably some dumb typo that I can’t find but that still doesn’t explain why it works flawlessly on my local install which led me to believe I could release 1.2.0 without issue.

Sorry for the headache.

Well, if you read all my ranting tweets from this morning, you know this issue almost brought me to introduce Mr. Fist to Mr. Wall 😊 I have no clue why it isn’t reading the settings. I have this working perfectly on a local install, but like you, I installed this on a site this morning and got the exact same errors. For now I may have to pull the MSM out - but I ran into a further problem when I tried commenting all that MSM stuff out…I got an error on “$this->settings[‘css’]”, which means it basically cannot read the settings at all - and there are only three basic settings: enable, css, and check for updates. This is probably some dumb typo that I can’t find but that still doesn’t explain why it works flawlessly on my local install which led me to believe I could release 1.2.0 without issue. Sorry for the headache.

I must have missed your ranting tweets this morning! 😉

It’s not problem at all. Nothing essential to our daily activity. I hadn’t actually made the previous version of dulee noted live yet. Just experimenting. Good luck on finding the problem. If I knew PHP at all I’d jump on board to help you out.

You must not be following my personal twitter account, which is full of saucy stuff and salty language (I don’t rant on the masugadesign twitter account - or really respond to people with that account - I’m lucky I even saw your response there this morning).

I just upgraded my local install to the latest version of EE and uninstalled/re-installed 1.2.0 and everything still works fine (locally I’m running MAMP with PHP 5). What version of PHP is the server running? I think the server I tried mine on that wasn’t working was running PHP 4.

Wow. PHP 4 it was. Stupidest oversight ever on my part. Glad I didn’t punch that wall. MD Dulee Noted 1.2.1 bug fix release out now with fix for PHP 4. Visit the download page for MD Dulee Noted.

It’s now working like a charm on the site I was struggling with this morning.

Yeah, you’re right, I don’t follow your personal tweets. I’ll add you now.

Sorry I couldn’t get back here earlier to give you the PHP version number.

I downloaded it again and installed it and yes, everything is working great now! Thanks for taking care of that. This is going to come in extremely handy for our users.

There’s much more action on my personal twitter account 😉

Sorry for the PHP 4 oversight - that simple copy/paste error cost me my morning, but now this is a solid release.

I just created a new site in MSM and MD Dulee Noted is throwing this error: Notice: Undefined index: 8 in E:*path*\extensions\ext.md_dulee_noted.php on line 89

This is line 89:

$settings = ($return_all === TRUE) ?  $SESS->cache['mdesign'][MD_DN_addon_id]['settings'] : $SESS->cache['mdesign'][MD_DN_addon_id]['settings'][$PREFS->ini('site_id')];

Even though when I went to preferences, it said it was enabled for the new site. I suspect the variable was NULL instead of “No/False” or “Yes/True” until I hit “Save” and the error went away. So, no problem now - just FYI.

-dhl

I’ll bet that’s the only time you would see that error. Thanks for pointing it out. Noted for the next time I make changes or upgrade in any way.

Great extension, Ryan. It will drastically simplifies the instruction manual I generate for each client.

Is there any chance you could also make it work for the category custom fields?