PDA

View Full Version : v1.5.x - WYSIWYG Editor Admin Addon


raminia
12-18-2005, 08:13 PM
Notes
I made a WYSIWYG editor for PP out of tiny mce.

If you don't like this addon but you like to have a WYSIWYG check out this FireFox extention:
https://addons.mozilla.org/extensions/moreinfo.php?id=1449

Download Link
http://www.pixelpost.org/v1/index.php?x=downloads&details=138

Instructions
Copy contents of To_Addons into the addons folder of your photoblog and your done! Enjoy!
http://www.pixelpost.org/v1/devfiles/31_wysiwyg.jpg

Joe[y]
12-20-2005, 04:37 PM
did you test this in MSIE ramin? it reads the html source output for the menu as an error or something and displays nothing whatsoever.

blinking8s
12-20-2005, 05:10 PM
i imagine it would conflict heavily with markdown as well, and one wouldhave to be switched off when the other is in place. but i donno, it just makes sense in my head...

raminia
12-20-2005, 05:52 PM
']did you test this in MSIE ramin? it reads the html source output for the menu as an error or something and displays nothing whatsoever.
whoops
I didn't test it in IE.

I don't think it will conflict with markdown since it uses html codes.

Battin
01-07-2006, 08:41 PM
can you make it work.. ? i really want something like that.. i use firefox.. it doesnt work! :(

raminia
01-07-2006, 08:43 PM
do you have PP version 1.5?

Battin
01-07-2006, 08:49 PM
yes... one moment.. i will just try it again..!

Battin
01-07-2006, 09:06 PM
Fatal error: Call to undefined function add_admin_functions() in /usr/home/web/web50725/blog/addons/admin_WYSIWYG.php on line 21


it says so under Addons in admin panel... and my blog goes all white.. :(

raminia
01-07-2006, 09:10 PM
that means that you don't have 1.5 but 1.4 OR you did not copy all files and upgrade completely.

Battin
01-07-2006, 09:21 PM
hmm yes it seems like i only have 1.43... but where do i get 1.5 ?? you can only download 1.43 on pixelpost.org

raminia
01-07-2006, 09:25 PM
yeap sure:)
but it's in BETA stage: PP 1.5Beta (http://forum.pixelpost.org/showthread.php?t=2922)

btw, if you don't want to upgrade the whole blog you can use this modification (http://forum.pixelpost.org/showthread.php?t=2675) to use the WYSIWYG editor.

alucard
01-11-2006, 11:41 PM
yeap sure:)
but it's in BETA stage: PP 1.5Beta (http://forum.pixelpost.org/showthread.php?t=2922)

btw, if you don't want to upgrade the whole blog you can use this modification (http://forum.pixelpost.org/showthread.php?t=2675) to use the WYSIWYG editor.

hi I am running 1.5Beta, but unable to install WYSIWYG addon. I get the same error as given above.

thanks.

dakwegmo
06-17-2007, 02:08 AM
Just an FYI for anyone using this addon. I discovered a little bug with this addon and PP1.6. With this addon enabled, if you try to resize your thumbnails, you get an error that the selection wasn't entirely on the image. Even when it clearly is. I found that I had to set the bottom edge well away from the bottom of the fullsized image in order to prevent this message. Making no other changes except for disabling the addon allowed me to crop all the way to the bottom.

Lucifer
07-01-2007, 09:56 PM
12CropImage error

Image crop area becomes different. PP1.6.. :(

Is no there solution?

jaywilliams
07-02-2007, 12:54 AM
Try adding this code to the JavaScript:

<script language="javascript" type="text/javascript" src="../includes/tiny_mce/tiny_mce.js"></script>
<script language="javascript" type="text/javascript">
tinyMCE.init({
mode : "textareas",
theme : "advanced",
theme_advanced_buttons1 : "bold,italic,underline,separator,strikethrough,just ifyleft,justifycenter,justifyright, justifyfull,bullist,numlist,undo,redo,link,unlink",
theme_advanced_buttons2 : "",
theme_advanced_buttons3 : "",
theme_advanced_toolbar_location : "top",
theme_advanced_toolbar_align : "left",
theme_advanced_path_location : "bottom",
extended_valid_elements : "a[name|href|target|title|onclick],img[class|src|border=0|alt|title|hspace|vspace|width|h eight|align|onmouseover|onmouseout|name],hr[class|width|size|noshade],font[face|size|color|style],span[class|align|style]"
});

// Fix bug with 12CROPIMAGE
libinit();
</script>

Note the addition of the following lines:
// Fix bug with 12CROPIMAGE
libinit();