No need to respond to my question here–I just found the thread on field formatting problems in 1.6.5 (http://ellislab.com/forums/viewthread/96291/).
[EDIT]: On my install, I think I’ve corrected the issue by inserting the following code (graciously provided in the aforementioned thread) just after line 376 of ext.markitup.php:
$r .= $DSP->input_hidden('field_ft_'.$row['field_id'],$row['field_fmt']);
Yep…there is definitely an issue going on and I was going to point you to that thread. Can’t seem to get a definitive answer on solving it, for some reason. 1.5.2 is pretty much ready to go - but I have to make sure it works with this formatting issue. I need Markitup to work as bad as you do (especially on my current build), so I’ll be working on a fix as soon as I am able.
I just installed this on my local server (xampp). I’m positive I haven’t missed a step, but I’m not getting the markitup buttons to appear and on the top of my screen I get the following errors:
arning: opendir(extensions/markitup/sets/) [function.opendir]: failed to open dir: No error in D:\path\to\system\extensions\ext.markitup.php on line 171
Warning: readdir(): supplied argument is not a valid Directory resource in D:\path\to\system\extensions\ext.markitup.php on line 173
Warning: closedir(): supplied argument is not a valid Directory resource in D:\path\to\system\extensions\ext.markitup.php on line 187
Sean, I’m not sure if you can wait a day or two, but I have the first version of this extension (MD Markitup 1.5.8) ready for release. It will be commercial.
As for the version you are trying to install, you may want to go to those lines in the extension and hard code any paths to your directory. The newest version of MDMIU is so different from the version that’s out there that they’re almost two different extensions.
@richard: Did you rename the settings variable in textile/set.js to “mySettings_textile”? Also, you put the markitup folder inside your extensions folder? And you DID download the Textile set from Markitup, didn’t you? 😉 I might do a screencast showing how to install this from start to finish, as I think that would probably answer a lot of questions for everyone.
I did all this too but I just get the Disable Markitup link.
Ryan, hope your new year is off to a wonderful start.
I’m using 1.0 on my an install that is running ExpressionEngine 1.6.6 Build: 20081114. This is on a site in development that currently has little to no user interaction with it with the exception of the project team.
It took me a little while to get it working the way I wanted it to but I eventually got it up and running without flaw (so I thought) about a month ago.
All has been fine until today. After a brief hiatus (not being in the system for several days), I logged in and was greeted by
Notice: Undefined offset: 1 in /home/womenach/public_html/cms/extensions/ext.markitup.php on line 567
Repeated 141 times (I actually counted 😊 ) This error only appears on the CP homepage. I disabled “Check for updates?” in the settings to see if that might have an affect but no go. I’ve also disabled all my other extensions to see if this error was due to a conflict but this too did not rectify the situation.
The Markitup field is not showing up either but the field type is still designated.
Just wondering if you might have some advice on where to dig around?
Thanks
OK, first of all - please don’t use 1.0 😊 I’ll be putting the commercial version of MD Markitup 1.6.0 (the first commercial release) today - tomorrow at the latest. There have been an incredible amount of changes. If you want to get it now, PM me and I’ll give you info for my PayPal account.
So sorry it took me so long to get the commercial version together. Using 1.0 is highly discouraged! I have no idea what that error is or why, and 1.0 is no longer supported - especially because line 567 doesn’t mean anything anymore and debugging that would be more than difficult!
Please see the page I just made live about 10 minutes ago: MD Markitup.
Please make sure, if you decide to purchase MD Markitup, that you review the included changelog so that you get an idea of what has been added or updated since 1.0.
I will be working the rest of the day on updated documentation. However, if you need any help in the meantime, just email me and I’ll help you out.
I’m testing v1.6 on an XHTML field. I’m clicking on the options for images and I get these errors:
mcImageManager is not defined [Break on this error] manager: mcImageManager, set_textile.js (line 37) [Exception… “Component returned failure code: 0x80520012 (NS_ERROR_FILE_NOT_FOUND) [nsIFileInputStream.init]” nsresult: “0x80520012 (NS_ERROR_FILE_NOT_FOUND)” location: “JS frame :: chrome://retailmenot/content/rmn-networkhandler.js :: anonymous :: line 86” data: no] [Break on this error] jQuery.readyList.push(function(){return ….url,s.async,s.username,s.password);else jquery.min.js (line 27) RMNPrefs is not defined [Break on this error] jQuery.readyList.push(function(){return ….url,s.async,s.username,s.password);else jquery.min.js (line 27)
I’ve also inserted an image from the EE file browser, then highlighed the image and clicked and nothing happens there either. Should something be happening?
Now, I do happen to have mcImageManager so I could define it wherever that needs to be done. Also, it’s a little odd that I have XHTML as the field type and the error is from Textile.
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.
OK, the Moxiecode Authentication Extension has a home at Masuga Design, so I removed the file from this post to keep things tidy.
(Initial Moxiecode Auth. Extension developement credit goes to Tim Kelty at Geniuscar.)
I’ve been testing the beta of this new version for the last month or so and it’s fantastic. Ryan has put in a ton of work and I’d highly recommend this Extension. It allows for tons of customization and flexibility. Using it with the ImageManager and FileManager really provide a great combination of tools for clients.
Show some support and go purchase a copy if it fits your needs. Great work Ryan!!!
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.