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.
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
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.
That’s a good question. I’m not sure there’s an available hook to be able to add this type of field to the custom category fields - so, right now I don’t have an answer for that.
I’m not sure there’s an available hook to be able to add this type of field to the custom category fields
Ryan, have you had a chance to check? I am using Category custom fields extensively in some projects and it would really help the editors to have some help statement into the Category dialog box. If it is possible, I may finance the additional development.
I actually just came upon a need for this myself only yesterday. I’ve never really used the category custom fields before, but the second I went in to use them I realized they do not have any instructions - so at least an MD Dulee Noted field at the top could help things out.
The main problem I see is that even if there IS a hook, MDDN uses the existing instruction textarea for a field - and there simply isn’t one here to use. I’m not clear where the instructions would be stored.
Well…at the minimum, your MDDN custom category field could display a text area for us to enter instructions. When displayed in the Category editing window, it could then have a different style than the others and be not editable.
Does that textarea require a new, separate, MDDN table to be created then? If there is no instruction field already there to populate and I have to manually make a textarea appear - I’m just wondering where I’m actually storing the data that you would enter there. I’d have to either make a new table or add a column to the existing exp_category_fields table, or something similarly crazy.
Maybe the thing to do is put in a feature request for Custom Category Field Instructions?
I cannot help you about this, Ryan. ‘Not a EE extension developer or even expert programmer. I am on the user interface/consulting side of this business. Let me know when you had time to evaluate this further. Thanks!
I hear you on that. I looked at the category custom fields table and there is just nowhere to put this information. Unfortunately it’s structured differently than the regular custom fields table.
I agree that this area could use instructions as well as other custom field types, but I don’t think it’s possible at this point.
Ryan, I see myself repeating a lot of instructions from Weblog to Weblog.
Would it be possible to add a server-side include command into the field? That would allow me to write/edit these instructions into an include file to call wherever I need it.
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.
