Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
#889 2011-08-02 08:25:45
Re: glz_custom_fields
Gerhard, might be wise to pull this version of the plugin until a pref is put in place to disable/enable the tracking code – and have it as an opt-in (ie. a user has to enable it) feature going forward.
I’m sure that will keep everyone happy.
Offline
#890 2011-08-02 08:41:42
- Dimitri
- Member
- From: Johannesburg
- Registered: 2010-10-31
- Posts: 129
Re: glz_custom_fields
I agree with Phil.
I am getting a lag when working offline. Would prefer to disable the tracking code
<txp:way_too_cool />
Offline
#891 2011-08-02 08:45:12
Re: glz_custom_fields
I don’t think that I was clear enough about the tracking code. It doesn’t show me anything else but active users (no different to Google Analytics). The only twist is that its real-time. It gives me details about the user agent etc.
Since this proves to be a rather controversial issue, I will indeed pull the version and add the tracking code as an opt-in. Thanks for the suggestion Phil!
Offline
#892 2011-08-02 08:54:40
Re: glz_custom_fields
Dimitri wrote:
I am getting a lag when working offline. Would prefer to disable the tracking code
On my machine, when working offline, the first requests takes 7ms to fail, the second one 238ms.
Still, tracking code enabled by default, without explaining its purpose, does feel a bit odd in retrospect.
Offline
#893 2011-08-02 09:23:40
Re: glz_custom_fields
Cheers Gerhard, look forward to the re-release.
I’ll just add that glz_custom_fields is essential to pretty much every Textpattern site I build so keep up the good work.
Phil
Offline
#894 2011-08-02 09:34:23
Offline
#895 2011-08-02 11:59:15
Re: glz_custom_fields
glz_custom_fields has been essential to every site I’ve built over the last year…. and the rest :)
If you gain some insight for improvement whilst tracking, I have no problem at all – but I think the offering the preference is probably the way to go.
I have installed a copy of glz_custom_fields 1.2.5 on a site without any problems on an existing site – but this isn’t showing in your stats… its still in dev so not live…. should it be?
Offline
#896 2011-08-02 14:20:00
Re: glz_custom_fields
- opt-in: good
- tracking code: meh
- my dot on your map: no worries
- complying with german laws: prolly important
- using a current version of glz: priceless.
Keep up the excellent work. I’m looking forward to seeing what you have under your hat for this plugin.
Last edited by mrdale (2011-08-02 14:21:45)
Offline
#897 2011-08-03 00:27:27
Re: glz_custom_fields
I did not have a chance to download the new version before it was pulled, so I didn’t get a chance to attempt an upgrade.
Regarding this statement:
As a word of caution, all existing plugin preferences will be overwritten on install. This is related to the way path/urls are now saved in the db.
What should we do to make sure our existing installations stay awesome when we upgrade? Are there special instructions?
The readme file might have offered answers to all my questions— I don’t know. If that’s the case, I’ll look into it when the plugin comes back.
Offline
#898 2011-08-03 03:20:49
Re: glz_custom_fields
I was disappointed that I didn’t have it for a new install today as well – Gerhard can track me to his heart’s content. :)
Offline
#899 2011-08-03 03:35:19
Re: glz_custom_fields
I am tracked by my iPhone, my iPad, anti theft devices in the cars, GPS locators on the collars of 3 Vizslas that are never more than a few feet away and apparently by a nosy neighbor who always seems to know where I am before I do. Welcome to the throng Gerhard and thank you from the bottom of my heart for your truly excellent plugin.
Last edited by joebaich (2011-08-03 15:21:47)
Offline
#900 2011-08-03 15:17:51
- element
- Member
- Registered: 2009-11-18
- Posts: 99
Re: glz_custom_fields
Tracking code or no tracking code, the plugin is awesome. I also prefer opt-in for tracking btw.
I have another question. While the previous version required the files to be in the ‘scripts’ directory, the new version must use a new directory called ‘plugin’?
Why the change?
Offline