great plugin Afwas, will do good for many purposes, may come handy at any time.. thank you very much B)

edit: tested right away, working great

I found a bug.
Opera 9.26 Win

http://img167.imageshack.us/img167/7822/operawp7.jpg

Thanks sam2kb,

Confirmed in Opera 9.25 on Ubuntu 8.04

I don't and haven't used this enhancement, but way back in the day the same problem - foodles of [+] boxes - happened and I'm pretty sure it was overcome. Sadly, I've no info on *how* to overcome it. Searching diligently might be your friend?

i guess it doesnt work when you switch your skin.. i have made a few try, when i switch back to the skin when i installed the plugin; works again..

can anyone else try switching skins after installing this plugin and report back pls ?_?

it wasnt about the plugin... working good now..thank you again..

==========================================
just replaced

	'block_start' => '<div class="$wi_class$ bSideItem">',
	    'block_end' => '</div>',

with this

	'block_start' => '<li class="$wi_class$ bSideItem">',
	    'block_end' => '</li>',

I installed it, put the "collapse_me" into my category and linkblog widgets... and no change occurred.

http://www.comiclist.com/index.php/links/

it is likely to be about your skin.. probably sidebar.. may be u should tell us which skin you are using unless it is a custom one or post your sidebar.inc.php

cslepage, how come your widgets start with a <div> and not with a <li>? Did you hardcode the widgets in the sidebar?

Only for cslepage: try [url=http://www.blog.hemminga.net/media/blogs/plugins/cslepage_collapsable_categories_plugin.zip]this one[/url] instead.

Good luck

Afwas wrote:

cslepage, how come your widgets start with a <div> and not with a <li>? Did you hardcode the widgets in the sidebar? ...

For the sidebar container, only evopress and evocamp (of the package skins) use LI for block_start. All others use DIV.

Thanks EdB,

I hadn't noticed that one yet. ;) I don't think I am happy with it either :|

My skin is b2evo_ru, though I have modified it, but I certainly didn't hardcode these widgets into the sidebar.

I uploaded the new version you posted just for me, and I don't yet see a difference.

Could this be what tilqicom saw on March 29? And if so, where do I make the change they made?

Afwas wrote:

cslepage, how come your widgets start with a <div> and not with a <li>? Did you hardcode the widgets in the sidebar?
Good luck

Looking in sidebar.inc.php, that's the way the author wrote that file.

Hi cslepage,

Edb answered the queston regarding the <div> in stead of the <li> I expected. Can you keep the new version of the plugin up on your site, so I can (try to) debug it?

*edit*
Better: [url=http://www.blog.hemminga.net/media/blogs/plugins/cslepage_collapsable_categories_plugin.zip]download[/url] the plugin again. I did make some changes already. ;)

Thanks

Yes, absolutely.

Hi cslepage,

The new version seems to cure your problem on my testblog. In your blog I cannot see the plugin loaded correctly. If it were loaded correctly you would find this in the header:

<!-- START Stylesheet and JavaScript file for expandable Categories -->
<link rel="stylesheet" href="/plugins/collapsable_categories_plugin/mktree.css" type="text/css" />
<script src="/plugins/collapsable_categories_plugin/mktree.js" type="text/JavaScript"></script>
<!-- END Stylesheet and JavaScript file for expandable Categories -->

So do check the plugin settings, reload the plugin and try Tools -> Misc-> Delete prerendered item cache.

Good luck

The new version seems to cure your problem

It works for me too, I was going to post the fix when I saw your edited post ;)

Afwas wrote:

Hi cslepage,

The new version seems to cure your problem on my testblog. In your blog I cannot see the plugin loaded correctly. If it were loaded correctly you would find this in the header:

<!-- START Stylesheet and JavaScript file for expandable Categories -->
<link rel="stylesheet" href="/plugins/collapsable_categories_plugin/mktree.css" type="text/css" />
<script src="/plugins/collapsable_categories_plugin/mktree.js" type="text/JavaScript"></script>
<!-- END Stylesheet and JavaScript file for expandable Categories -->

So do check the plugin settings, reload the plugin and try Tools -> Misc-> Delete prerendered item cache.

Good luck

Looks like it is working for the linkblog, thanks!

Yes, working great now.

have fun

Is there any way to display collapsable categories opened by default ?

Hi slamp,

Have a look at this very early version of [url=http://www.blog.hemminga.net/media/blogs/plugins/jquery_treeview_plugin-0.1.zip]jquery_treeview_plugin-0.1.zip[/url].

Have fun

this is really weird for me, as i ve previously got this category plugin working in my other website perfectly..

i am getting this view:

http://i30.tinypic.com/2cz9ffn.jpg

I thought it might be because of sidebar li properties however whichever skin i use the problem persists, this is so strange, i wonder what might cause this to happen

@Afwas:
On FF, it works. Just a problem with the last category. I'm using evopress skin.
http://slamp.free.fr/b2evo/jquery_treeview_collapsed_evopress_FF2.png
http://slamp.free.fr/b2evo/jquery_treeview_evopress_FF2.png

I got error with IE

@tilqicom,
You have a curious problem, caused by gathering categories from different blogs. Only the first blog is collapsing. The sturcture is like:
<li>
<ul>
<li>
<li>
</ul>
<ul>
...
</li>
This second <ul> is caused by the second blog and the widget is trained to act on the first <ul> only.

@slamp:
I noticed the same problems on evoskin. This is caused by the original style applied to the list. I haven't found a way yet to get rid of this style before the widget acts on it.

It's works great on asevo, custom, nifty_corners, natural_pink, miami_blue.

There is a problem on evo_camp
http://slamp.free.fr/b2evo/jquery_treeview_evocamp_FF2.png

Is there a way to display the + but not the dot ?

There is a way this can be worked out, but it would require people to edit a file to make it happen.

Root cause is that the plugins affect the document head way early in the process, meaning any styles applied get over-ridden by styles that come later. Specifically, and only looking at the bits that matter, _html_header.inc.php has this:

	<?php $Plugins->trigger_event( 'SkinBeginHtmlHead' ); ?>
	...
	<link rel="stylesheet" href="style.css" type="text/css" />
	<?php include_headlines() /* Add javascript and css files included by plugins and skin */ ?>
	<?php
		$Blog->disp( 'blog_css', 'raw');
		$Blog->disp( 'user_css', 'raw');
	?>

IF a user were to edit that file in their skins/ or skins/yourskin/ folder to the following bit then the plugin could supply style instructions that would over-ride the default instructions in the skin.

	<link rel="stylesheet" href="style.css" type="text/css" />
	<?php $Plugins->trigger_event( 'SkinBeginHtmlHead' ); ?>
	<?php include_headlines() /* Add javascript and css files included by plugins and skin */ ?>
	<?php
		$Blog->disp( 'blog_css', 'raw');
		$Blog->disp( 'user_css', 'raw');
	?>

In a perfect world, the file would be a bit more intelligent than just this, but for the purpose of this thread I believe this would allow the plugin to properly work with the nested UL situation.

I think. That's my problem most of the time yah? Like for example I thought if I took a week off for Memorial Day weekend I could maybe do some flying but it turns out this weekend decided to be super-rainy and ultra-windy. :'(

Wait a minute - stop the presses!

It looks to me like the add_headline() function can do the job, though I don't know how it gets used. I do not know of any plugins using that function, but the evopress and nifty_corners skins are using it to add bits via the include_headlines() function, so maybe it is possible for an intelligent* person to make a plugin take advantage of that feature?

* "intelligent" means someone like Afwas or sam2kb or even the script kiddie known as Yabba - not me.

Thanks EdB,

You're right. I found that one already. It's nephews are require_js() ans require_css(), both are added at the bottom of the <head> section.
The add_headline() is for plain code as in:

add_headline( '<script type="text/javascript">
    // your code goes here
</script>' );

Here are some more examples:

require_js( '#jquery#' );
require_js( '/plugins/foo/bar.js', true ); // true makes relative to baseurl,
                                           // default false searches for js in /rsc/js/.
require_css( 'basic.css' ); // false -> searces in /rsc/css/
$foo = '<style type="text/css">
  // your style
</style>'
add_headline( $foo );

This may solve some of the troubles. However the evopress skins uses custom bullets. In the added style for the new plugin I have

list-style: none;

to reset the bullets, but that doesn't work on the custom bullets from the evopress skin. No doubt the problem with the evocamp skin is similar. It does work on the 'custom' skin however.

So I did look at it from the point you mentioned in the new plugin. I haven't found a 'this solves all problems' answer yet.

I already tried this but nothing really happens. I'm using evocamp please help.

I will look at it this weekend.

Hi Guys,

I was wondering if you can have a look at my testskin and help me out with an issue. I've got the expanding categories working correctly - but some reason it only works on the first blog. Once the second blog list starts it reverts back to having all categories shown.

Thanks for the help,
Akgbob

Here's the link: http://www.leenaeats.com/blog/index.php?tempskin=LE2

Hi akgbob. I'm seeing it do the collapse thing just fine on both the first and additional pages of your blog posts.

Oh and I totally dig on that skin!

Firefox 2.whatever, enabled javascript cuz I had to.

Thanks for the compliment - its a skin a made awhile back - pretty but the codes a bit of a mess. Finally getting around to cleaning it up and updating for the newer perks of 2.x

Let me clarify my statement. If you look at the categories its broken out by "Leena Eats This Blog" and "Chicken n' Waffles". Some reason the expansion works on the Leena Eats categories, but it didn't work on the CNW categories. Here's what I'm looking at:

http://www.leenaeats.com/Images/example.jpg

Thanks again for the quick reply!

I should rewrite that bloody thing. You have no idea how much I've struggled with it to get it where it's now. I'll have a look at the end of the week or early next week. Somebody remind me please.
Can you please check if a second install of the plugin helps here?

Good luck

No worries - thanks for all the work you've already put into it!