Page 1 of 1
track exit & extendid properties for entries plugin
Posted: Tue Dec 06, 2005 12:20 am
by Guest
I noticed that when I install the "extendend properties for entries" plugin, the track-exit plugin is not counting anymore... After removing the plugin everything is working fine again.
Re: track exit & extendid properties for entries plugin
Posted: Tue Dec 06, 2005 12:20 am
by BabeSpot
Anonymous wrote:I noticed that when I install the "extendend properties for entries" plugin, the track-exit plugin is not counting anymore... After removing the plugin everything is working fine again.
That was me again ...
Re: track exit & extendid properties for entries plugin
Posted: Tue Dec 06, 2005 1:33 pm
by garvinhicking
What were your settings for the extended entryproperties plugin? Did you enter anything in the advanced options screen?
Are links to webpages still pointing to "exit.php" when you have the plugin enabled?
It's not meant this way, but I know several installations were track exits and the entryproperties plugin co-exist.
Regards,
Garvin
Posted: Tue Dec 06, 2005 2:01 pm
by BabeSpot
No I didn't enter anything in the extended properties screen (yet), but noticed that the URL's in my entries on my site (I clicked a few to test them) were indeed NOT pointing to exit.php anymore, but just to the plain HTML url in the entry.
Posted: Tue Dec 06, 2005 2:04 pm
by garvinhicking
Then I guess you enabled the entry cache of the plugin (don't know if it's on by default)...
Check your plugin section, the Track Exits plugin must appear BEFORE the extended properties plugin so that it properly tracks exits.
You are running Serendipity 0.9.1?
Regards,
Garvin
Posted: Tue Dec 06, 2005 2:15 pm
by BabeSpot
garvinhicking wrote:Then I guess you enabled the entry cache of the plugin (don't know if it's on by default)...
Check your plugin section, the Track Exits plugin must appear BEFORE the extended properties plugin so that it properly tracks exits.
You are running Serendipity 0.9.1?
Regards,
Garvin
Yup, 0.9.1 here... But I guess it had something to do with the cache entry stuff. I tested that plugin too...
Grtz