ronbme
Forum Replies Created
-
Forum: Plugins
In reply to: [Plugin: Custom Post Type UI] Version 0.4.1 partially working with WP3 Beta 1gambit37,
Why do you have your permalinks set to /%posttype%/? I would set that to /%postname%/, or just use the default until you get things working.Also, do you have the network option, multi sites, set up on your build?
If you’re getting a 404, it would seem that the path is not being found.
Ron
Forum: Plugins
In reply to: [Plugin: Custom Post Type UI] Version 0.4.1 partially working with WP3 Beta 1smakdaddy, I’m running locally too.
You might want to put a copy of jquery.min.js in the same directory with the plugin. Then you’ll need to edit the line in the plugin which references an external jquery.min.js file. Like this:// <script type=”text/javascript” src=”http://ajax.googleapis.com/ajax/libs/jquery/1.3.0/jquery.min.js”>
<script type=”text/javascript” src=”jquery.min.js”>You can just comment out that first line and make a new line with what I have.
That will allow you to view the “Advanced Options” for Custom Post Types and Taxonomies.
Not sure why you are getting the “invalid function” error.
mark8barnes, I just did a complete reinstall yesterday. Still not having that problem.
One thing you and smakdaddy could check is to make sure that you have “administrator rights”. If you don’t, that is the problem.
Ron
Forum: Plugins
In reply to: [Plugin: Custom Post Type UI] Version 0.4.1 partially working with WP3 Beta 1I tried to duplicate this error but couldn’t.
What it looks like is that the custom post type wasn’t created in the first place. That would also account for the error you got when trying to access “Manage Post Types”. There weren’t any new types created so it threw up an error. (But, if that was the case, you should have gotten an error saying there were no new types created.)
One thing to keep in mind is that you are working with a beta version of WordPress. Something which worked ok yesterday might not work after you upgrade to a newer build.
Forum: Plugins
In reply to: [Plugin: Custom Post Type UI] Comments about version 0.4.1Also, when editing a custom post type, the button should say “Save Custom Post Type”, not “Edit Custom Post Type”.
Same thing for “Edit Custom Taxonomy”. It should say “Save Custom Taxonomy”.
Forum: Plugins
In reply to: Front-end Editor and ScbFrameworkI’ve got several versions of WordPress I’m working on, but mainly I’ve been testing these on ver. 2.9.2 before I try them on ver. 3.0.
I haven’t really used scbFramework yet. I’ve written a plugin for custom post types and I was going to use it for some other plugins for custom post types and taxonomies.
I’m also testing out some plugins for other authors and I thought I might be able to use it on some of those.
I’ve been trying to keep the number of plugins down on my WP 3.0 site, so I can determine whether bugs are in the core or a plugin.
Just setup the network on WP 3.0 with the Super Admin access. I’m going to create about 10 – 15 sites and set up each one differently.
Too many irons in the fire. Too little time. ð
Ron
Forum: Your WordPress
In reply to: New photography and video siteDon,
I can’t believe others have not asked you to share how you created your site.
I would be interested in knowing how you created it, especially the front page. The header and menu are very well done.
If you get a chance, please give us details how you did it.
Forum: Plugins
In reply to: [Plugin: Elastic Theme Editor] json errorwaltkania and veehikle,
Your problem is the same as tanc’s. This plugin does work under WP 2.86 and WP 2.9. The developer is working on it.
There is also a potential problem some people may have with an extension on their servers. I’m working on this to confirm it.
Ron
Forum: Plugins
In reply to: [Plugin: Elastic Theme Editor] json errortanc,
Your problem is a conflict between the json.php file in the Elastic plugin directory and the class-json.php file in the wp-includes directory.
Disabling plugins isn’t going to help.
I’m not the developer but this is a great little plugin. I’ve got it working on a Windows server and on a WAMP server locally, using WP 2.86 and WP 2.9.
One problem was with the correct directories not being found. I’ve notified Daryl (the developer) and he is fixing this.
I think you’ll like what you see when you have this up and running. Like anything that is cutting edge, there will be always be little bugs to work out with different server combinations.
Ron
Forum: Fixing WordPress
In reply to: RSS Error: XML Error on my DashboardYes, I am getting the error too. I get it on different versions of WP using different plugins, so I assume it is on their end.
Has anyone informed them that they have a problem?
Forum: Plugins
In reply to: Plugin: Elastic Theme Editor – No Response in 2.8.5I finally got this plugin working under Wampserver. Someone else also asked for this.
Rather than repeating it here, go to this link to see what I did.
Forum: Plugins
In reply to: Plugin: Elastic Theme Editor – No Response in 2.8.5Forum: Plugins
In reply to: [Plugin: Elastic Theme Editor] issues on WAMP serverI got it working on a Wampserver using Windows XP.
All of the edits are in “class-elastic-editor.php”.
1. Look for the line “$plugin = Elastic_Editor::get_folder();”
Around line 46 under “function init_styles() “2. Replace that with ” $plugin = basename(dirname(__FILE__)); “
(without the quotes)3. Now look for every instance of ” $plugin “
The next one should be ” WP_PLUGIN_URL .’/’. $plugin . ‘/jquery/ui/css/custom-theme/jquery-ui-1.7.2.custom.css’, ”4. You will need to add the ” ‘/’. ” before ” $plugin “
5. You will have to repeat this in “function init_scripts()”
6. I also had to copy the “framework” and “jquery” folders to the “plugins” folder.
Most of the reasons this plugin doesn’t work is because of errors in finding the proper directories. By using Wampserver I was able to examine the logs and find out what is happening.
This should get you up and running with the plugin.
Forum: Plugins
In reply to: Plugin: Elastic Theme Editor – No Response in 2.8.5I’ve been getting the same thing. I’m using Wampserver and Wp 2.8.6.
No matter what I click on in the Elastic editor, nothing happens. I think what would solve the problem would be to have a dummy theme to start with.
There hasn’t been any updates or info on the author’s site since August.
I’m willing to help him work on the project but I need a good starting point.
Forum: Plugins
In reply to: [Plugin: WordPress Menu Creator] Serious FlawActually the submenu items will show up. You have to use the ID which Menu Creator assigns. It is in the left, or first, column. This is the number which goes in the “Parent” box. And your subitems will have an “Order” of 0, 1, 2.
For example, if your first menu item is “Home”, you would have a “1” in the “Parent” box. (In this case you would have the address of your blog in the “Value” box, i.e. “http://myblog.com”.) The Type would be “External Link”. (You would need to make sure that Menu Creator assigned a “1” as an ID.) You would have a “0” in the “Order” box.
If your second menu item is “News”, the “Type” would be “Post/Page” and the “Value” would be the ID of your page supplied by WordPress. The “Order” would be “1”. The “Parent” should be “2”.
If you have a subitem under “News”, the “Type”, for example, could be “Post/Page” and the “Value” would be the ID of your page supplied by WordPress. The “Order” would be “0”, because it is the first subitem. The “Parent” would be “2”.
You also need to check and see if Menu Creator has actually created the menu item. (It doesn’t always do it.)
But the plugin is unstable at this stage and not worth the effort. When you delete a menu, it isn’t deleted from the database.
I would say the plugin has a ways to go before it is ready. Also, none of the videos or samples are on the website.
It would probably take less time to write your own menu system. But if you want to keep trying maybe the hints I gave you will help.
Forum: Plugins
In reply to: [Plugin: Events Calendar] Events not showing up in large calendar or widgetTry putting it after the following:
<div class="footer">and before the following:
</div>Also make sure that in your header file you have the following:
<?php wp_head(); ?>That should go before `</head> in the header file.