Serendipity Forums

I try the plugin "link list" and it makes me trouble:

The page reproduction (I hope it is the right word, in german I mean "Seitenaufbau") interrupts on these plugin: It takes one or two seconds, where the sidebars "stand still".

You can see it here http://blog.stephan.manske-net.de

There is no difference if I use "dtree" or "plain CSS" or cached or not.

Hi!

Yeah, both dtree or CSS use the linklist.js file, and the JS loading can be responsible for the load time, I think...at least dtree is really hard on the DOM.

Can you set it to "plain" and tell me once you did that?

Regards,
Garvin

"plain"? There is only "dtree", "css list" and "simple css"


I try "simple css" - meanwhile the whole site seems to be faster (perhaps my hoster did something because I report that my blog is not realy fast at all) - but there is IMO still a slight interrupt at the link-list.

Hi!

Okay, the loading should no longer be related to the plugin.

Which other event and sidebar plugins are you running?

Best regards,
Garvin

garvinhicking wrote:Hi!
Which other event and sidebar plugins are you running?

many But are they important? If I delete the link-list-plugin there is no delay. If I place the link-list to the right sidebar, the whole left bar comes quick, and then only the right side delays on the link-list.

You can see it on my blog.


Note: Hm, I see another blog in these forum here and there I see no delay: blog.webgurus.de/

What settings are you using for the linklist plugin? A screenshot would probably do.

Since you are using the admin interface to add links I would definitely recommend turning on the "Cache Sidebar" option. It does not respond well when you change the setting in the administration panel, so I would recommend setting the sidebar how you would like it to appear, and then turning it on, but I think it would help you quite a bit. The cache will then be updated every time you add a link on the "Manage Links" interface.

Also what database are you using? Have the indexes been created on the tables?. (Should be an index on dateind, titleind, and catind.)

turning it on, but I think it would help you quite a bit. The cache will then be updated every time you add a link on the "Manage Links" interface.

i turned it on, but *I* did not see a real difference. Do you see any?

Also what database are you using? Have the indexes been created on the tables?. (Should be an index on dateind, titleind, and catind.)

Mysql

Ok, so I started to write that I didn't see a difference, but now that I refresh it a few time I do kind of see a difference... It seems to be about the same as the tags plugin now.

Still a pretty good delay, and I'm not sure why it is there...
I use the plugin on my site with a lot more links then you do without the same type of delay. I am wondering if the javascript statement isn't part of the problem, like Garvin suggested initially.

Can you edit the files on your server?
If so, can you edit the serendipity_plugin_linklist.php file, around line 423 find this line: And change it to this: (That big line should be all one line) If you can't edit the file for some reason let me know and I can send you a version with the changes in it to test.

Basically, I forgot to exclude the javascript reference if you choose Simple CSS. If it helps your page I will update the plugin in CVS.

I will try it tomorrow

My website also loads quite slowly today.

I tried updating linklist for a couple of days, but it failed. I don't think Spartacus has been down all the time.

I went to
http://spartacus.s9y.org/index.php?mode ... sidebar_en
but here there is only the event plugin for linklist, but not the sidebar plugin.

I do need both, don't I. Mix up?

Hi!

Actually both plugins are combined in the same zip file.

Best regards,
Garvin

I only see the event plugin, but not the sidebar plugin in the zip file.

I installed only the event plugin, but link list did not work

I have now taken the event plugin (Version 1.10) from the zip file. And downloaded the sidebar plugin (Version 1.8 ) via Spartacus, which now works again for me.

Now linklist works. Are those the two latest versions?



I recreated my blogroll by entering the xml data directly. However, I would like to switch now to "use a webpage to manage links" so that I can more easily add new links or delete old ones.
If I switch now, then all the links that I just recreated get lost. I do not want to recreate my blogroll manually by reentering each link on that webpage.
Is there a trick?


CSS List is faster than dtree, right?

Josh wrote:I have now taken the event plugin (Version 1.10) from the zip file. And downloaded the sidebar plugin (Version 1.8 ) via Spartacus, which now works again for me.

Are those versions backwards? I have:
Sidebar: version: 1.10
Event: version: 1.8

Josh wrote:I recreated my blogroll by entering the xml data directly. However, I would like to switch now to "use a webpage to manage links" so that I can more easily add new links or delete old ones.
If I switch now, then all the links that I just recreated get lost. I do not want to recreate my blogroll manually by reentering each link on that webpage. Is there a trick?

Ah ha! Yes, there is a trick... I didn't want people overwriting data accidentally, so the import only works when the serendipity_links table is empty. The easiest way to do this is to backup your xml, then switch "Enter XML directly" to no, go to "Manage Links" and delete all the default links, then switch "Enter XML directly" back to yes, paste in your xml and then switch "Enter XML directly" back to no.

Your links should be imported...

Josh wrote:CSS List is faster than dtree, right?

Um, no, not exactly...
The backend processing for both dtree and CSS List are identical (to generate the xml).

The sidebar processing (to render a display) for dtree is probably faster now (since the CSS list code has grown since I originally wrote it), and is certainly less memory intensive. Large dtree lists will also be smaller then equivalent CSS lists (because dtree doesn't send all the extra html tags to the client). However, dtree cannot be parsed by spiders, it requires a larger javascript file to be downloaded, and is more DOM intensive (the client renders the tree, rather than the server).

Personally, I use the CSS list because it is parsable, and that is the only feature I would say surpasses the dtree render version.