Jeremy Tarpley
Forum Replies Created
-
I think the lines from my error log are unrelated. I bet it has something to do with serializing / unserializing the contents of the text area uab_custom_description
If Font Awesome is being loaded by something else in WP and its causing a conflict, you can disable the UAB Font Awesome by adding the following in your theme’s functions.php:
// disable Ultimate Author Box plugin's version of Font Awesome function turn_off_uab_font-awesome() { wp_dequeue_style( 'uab-fontawesome' ); wp_dequeue_script( 'uab-fontawesome' ); } add_action( 'wp_print_styles', 'turn_off_uab_font-awesome', 100 );
Having the same issue and don’t think would be wise to modify the plugin code. Really hope a new version fixes this soon! Outside of this one bug, this is such a useful plugin!
Forum: Plugins
In reply to: [More Types] Best way to transition out of dormant 'more types' pluginI just had luck migrating to the Custom Post Type UI plugin. But I think these steps would probably work with any custom post type creator.
- Back up your database.
- Install Custom Post Type UI
- Create a new post type with the same settings as your current custom post type. Use a slightly different slug for the new post type. Ex. my old post type was external-news-link, new: external-media-link
- Export the content from your existing custom post type using the WordPress export tool (Tools menu > Export).
- Use a good text editor to open the export file.
- Run a find & replace on the file to replace the old slug with the new one. – Save.
- Run a WordPress import (Tools > Import) to import your modified file.
- Check to make sure everything is imported.
Hope that works for you! I’m sure there’s a smarter, more elegant solution out there but this worked in a pinch.
Well, gave up on this for now – found another plugin that does work with custom post types – File Icons. It hasn’t been updated in years but seems to work just fine with the latest 3.2.1 wordpress.
Same prob here. Haven’t figured it out yet either.
Forum: Plugins
In reply to: [Plugin: μAudio Player] uAudio Player not workingLooks like it would be great but I was not able to get this plugin to work with WP 2.7.1
I tried installing 0.6.2, 0.6.1, uninstalled all other plugins, added links to MP3s in posts & pages, used included Jquery, my own jquery, tried adding mAjQ = jQuery` to the top of microAudio.js.php – but nothing seemed to work.
Forum: Fixing WordPress
In reply to: I cannot enter codeChristy, I found a temporary fix:
- open wp-admin/admin-header.php with a text editor
- add the following somewhere inside the
<head>
tag:
<script type='text/javascript' src='<?php bloginfo('url'); ?>/wp-includes/js/tinymce/plugins/wordpress/editor_plugin.js'></script>
This is a total hack, I am sure this is not the proper place to add javascript includes. wp-includes/script-loader.php appears to be the proper script to add this. I am hesitant to edit this file for several reasons. First, I have only been using wordpress for a week so I am not familiar with how it works under the hood. script-loader.php looks to be a critical file used throughout WordPress so I didn’t want to break other things to fix this problem. Finally, I don’t know what caused this to break. The editor worked this morning. I made several hours of changes to wordpress today before realizing that it was broken. I suspect a plugin may have caused this problem but who knows…
——————————————————–
In case it is of use to someone, this is what I did to troubleshoot the problem (wordpress 2.3.2) :
When trying to edit any post (new or old), the Code tab did not work. When it was clicked, I noticed two javascript errors (using firebug). As mentioned in previous posts, the error is: switchEditors is not defined onclick(click clientX=0, clientY=0)
I searched for the text switchEditors in every file included in WordPress 2.3.2. It only refers to a javascript function in
wp-includes/js/tinymce/plugins/wordpress/editor_plugin.js
Viewing source for wp-admin/post.php reveals that the file: editor_plugin.js is not included in the <head> of the document. As a quick and dirty fix, I edited the header file for the posting pages: wp-admin/admin-header.php
Hope this helps.