Kyle - I’m willing to bet you have mcImagemanager installed but the scripts are not being loaded on the page (especially if you don’t already have one of Leevi’s LG Image/File Manager) fields on the page. Attached here is an extension that will help make sure you’re authenticated for Moxie scripts, and will also add the JS calls to the head for Moxiecode (see the settings). It’s not part of the Markitup package because you can certainly use markitup fields without using anything Moxie. I’ll put this Extension up for download on my site as well, but please give it a try. (Initial Moxiecode Auth. Extension developement credit goes to Tim Kelty at Geniuscar.)
Well that’s the weird part, I meant I own a copy of mcImageManager. It isn’t installed on this site though. I do see a lot of references to mcImageManger in the scripts, but I would prefer to set this up without it. I didn’t see any instructions on where to specify a path to mcImageManager, or how to tell the extension not to use it. I get the error using the default set and selecting the 1st image option that says “Image Left, Caption Left Insert new Pic”. Should this use another method of selecting an image if there is no mcImageManager present?
Oh, sorry! I assumed you wanted to use the Moxie Image manager. The set(s) come with a nested image button in there that is referencing the Moxie manager. (Boy I need to get the docs finished - too bad I was having so many other issues with download links today).
There’s a line I need to find between offering a set that has a lot of built in stuff that people may or may not use, and offering a set that is stripped down, making people have to turn everything on/add it themselves.
If you’re NOT using Moxie, you will have to use EE’s built in way to do images, like any other textarea (Upload Button, towards the top of the Publish/Edit screen) or you could use a basic image button (but typically those basic image buttons force you to have to know the url of your image, which for most clients isn’t ideal). That means that the included button may simply have to be altered or disabled, depending on what you’re trying to do.
If you want, I can send you a set file (or a set of all three set files…) that don’t have any references to Moxie in them. Maybe I should offer that as a download? Moxie-less starter sets?
Thanks Ryan.
I’m guessing people would like to have the option to use MD Markitup either with or without mcImageManager. I do like the option of adding the caption code in, so even if it’s not tied to mcImageManager the “wrapper” code is helpful. And if we could highlight an image url and click a button to get a dialog box to add title and alt attributes for images from the native file manager that would be great (just sayin’ 😉 ).
I don’t mind spending the difference for the mcImageManager, but I recall the setup being a little bit of a pain (I didn’t even know about that extension you posted…I guess that’s for that weird login issue). If your updated documentation will explain how to set up mcImageManager to work with it, I’ll wait for you to finish. I agree, the clients will not appreciate having to add a URL for an image using the default Markitup image button. I do like how it works fine with the native file manager unlike tinyMCE.
yes the moxie stuff. Will be buying Ryans Markitup for my next site 100% - but want to find out more about the moxie stuff mentioned here. - google didn’t seem to help very much - brought me to this thread again, but everything else didn’t seem relevant.
Sure, here’s the link.
Sean, I will be publishing an article at devot://ee in the next couple days (written by a guest author) that goes into detail about using Markitup and Moxiecode together - as I know this will become a popular combo, at least for EE 1.6.x. I’ve used them together - it can be crazy powerful, but I realize I’ll need to provide examples. (And I’d also LOVE to get real life examples of how people have used them together).
Moxiecode is the company that makes TinyMCE. They have an awesome File Manager and an incredible Image Manager. These, combined with some custom buttons on an MD Markitup field, gave the clients on my last project more power (especially with images) than I’ve ever seen with any other EE method. There is also a Moxiecode Authentication extension you may want to use when you’re using MD Markitup with Moxie stuff.
The Moxie stuff isn’t free, but for goodness’ sake if your client is going to be messing with images or files, I think the Moxie managers are well worth the investment per site. With all due respect I’ll never look back to using Mark Huot’s File extension as long as I have Moxie FileManager installed (which can also be used, at the same time alongside MD Markitup, with Leevi’s LG File Manager extension (and don’t forget Leevi’s LG Image Manager extension, too)).
Just when I wanted to write that
Using it with the ImageManager and FileManager really provide a great combination of tools for clients.
sounded interesting, I read your post Ryan. Looking forward to the article. We’ve always used TinyMCE in combination with Moxiecode’s Image- and Filemanager, eager to see how your extension does the job. Congratulations to a nice extension.
The Moxie stuff isn’t free, but for goodness’ sake if your client is going to be messing with images or files, I think the Moxie managers are well worth the investment per site.
Couldn’t agree more! On the last three sites, we had both managers installed, and especially the Image manager with its image processing capabilities is what clients just LOVE!
OK. I’ll bet that’s a problem with the preg_match_all in the show_full_control_panel_end function. sigh
I’m trying to see a pattern there. You know what’s weird. Your have one MDMIU field that starts with an ‘e’. The last two fields also start with ‘e’, but are immediately followed by underscores - and these are the ones that MDMIU is attaching itself to (incorrectly). I wonder if something weird is going on there with the underscore. I think I’ll have to try and recreate this with similarly named custom fields.
The query in MDMIU is this:
SELECT field_type FROM exp_weblog_fields WHERE field_id='".$DB->escape_str($field_id)."'LIMIT 1
Can you see if you can see the exp_weblog_fields table to see if “MD Markitup” is actually in there? I’m wondering if it’s just being drawn to the screen, or if it’s in the DB. I’d wager it’s just being output to the screen where it shouldn’t be. You could find the field_id of one of those borked fields (let’s say ‘34’) and go to Admin > Utilities > SQL Manager, click “Database Query Form” and run:
SELECT field_type FROM exp_weblog_fields WHERE field_id='34'LIMIT 1
Or click “Manage Database Tables” then browse the exp_weblog_fields table. See if anything in the field_type field is doubled up.
Thanks for including the version and build in your screenshot so I didn’t have to ask!
OK. I’ll bet that’s a problem with the preg_match_all in the show_full_control_panel_end function. *sigh* I’m trying to see a pattern there. You know what’s weird. Your have one MDMIU field that starts with an ‘e’. The last two fields also start with ‘e’, but are immediately followed by underscores - and these are the ones that MDMIU is attaching itself to (incorrectly). I wonder if something weird is going on there with the underscore. I think I’ll have to try and recreate this with similarly named custom fields. The query in MDMIU is this:Can you see if you can see the exp_weblog_fields table to see if “MD Markitup” is actually in there? I’m wondering if it’s just being drawn to the screen, or if it’s in the DB. I’d wager it’s just being output to the screen where it shouldn’t be. You could find the field_id of one of those borked fields (let’s say ‘34’) and go to Admin > Utilities > SQL Manager, click “Database Query Form” and run:SELECT field_type FROM exp_weblog_fields WHERE field_id='".$DB->escape_str($field_id)."'LIMIT 1
Or click “Manage Database Tables” then browse the exp_weblog_fields table. See if anything in the field_type field is doubled up.SELECT field_type FROM exp_weblog_fields WHERE field_id='34'LIMIT 1
I don’t see it in the database. I did change the field names so they don’t start with “e_” and that didn’t change anything. I think I’ll upgrade to 1.6.7 and see if that does anything. Edit: Nope on 1.6.7 now, still the same.
Thanks for including the version and build in your screenshot so I didn’t have to ask!
Figured I’d save me some typin’!
Question to everyone here: How would you prefer tech support? Are these EE forum threads really helpful? Brandon Kelly has an account at getsatisfaction.com for his addons now. Is there any interest in that? I just know how unwieldy these threads can get.
I think the get satisfaction is a good idea, but a link to the get satisfaction page at the beginning and end of your threads would be great as well as in your signature so it’s easy tofind for everyone.
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.