Hi,

There seems to be a conflict with Gypsy and Leevi Graham´s LG .htaccess Generator.

When I enter one of my custom fields, I am receiving this error:

Any ideas?

Cheers, Kippi

It did some testing and turned off all my extensions except for Gypsy and I still get errors

Using the latest version of EE (1.6.7 Build:  20090122)

Any clues?

Brandon Kelly - 20 January 2009 06:42 PM

I just set up a page for Gypsy on Get Satisfaction.

Going forward, please use that venue for support rather than the EE forums.

Thanks!

The “undefined index” issue has been resolved in Gypsy 1.0.6.

Ok, I thought I found a bug in Gypsy, then I jacked up my whole panel and thought my issues were related to my screw up. Then I went back and forth and tried to retrace my steps… I don’t think it’s a Gypsy bug. One thing I noticed though is uninstalling Gypsy leaves the two columns behind in the exp_weblog_fields table… shouldn’t it delete them?

Ok, no, it is defintely a bug. If the last field is a textarea, it blows up the Publish page even if the field isn’t a Gypsy field… why would this be? Did I mess up my CP somehow? Or is Gypsy still being called at some point during field rendering?

Nevermind, it isn’t a bug in Gypsy, it was with Publish Tweaks.

Brandon,

Great extension - can’t believe I missed its launch! And like many others I agree that this kind of functionality should really have been standard in EE.

@tilzinger LOL

Brandon Kelly - 19 February 2009 11:18 AM

@tilzinger LOL

It was a stressful morning

Great extension btw.

Simon Cox - 19 February 2009 09:44 AM

Brandon,

Great extension - can’t believe I missed its launch! And like many others I agree that this kind of functionality should really have been standard in EE.

Strangely enough it was b/c of this extension that I have a better idea of how the custom fields work and why they’re sort of in a direct relation to weblogs. (Searching can be a tricky affair with Gypsy fields, I prefer to just use it for non-searchable fields.)

tilzinger - 19 February 2009 11:39 AM

Brandon Kelly - 19 February 2009 11:18 AM

@tilzinger LOL

It was a stressful morning

Great extension btw.

btw see the Publish Tweeks thread, I’ve posted what could be a solution for you.

This is great. Does anybody have a tried and tested workflow on how to approach using this in a way that makes sense?

I have a few weblogs and don’t have a default field group assigned to them at all, and am just using Gypsy to exclusively extract the body, image, and a few other fields from a default group and pointing it to a respective weblog.

I’ve thought if I had some very unique fields I could make a secondary field group and exclusively just assign them through Gypsy.

Does this approach make sense?

Just wanted to add: Has anybody tried using Gypsy in an SAEF? Get Satisfaction doesn’t seem to have any answers to this question for 2 months. Will be giving it a go a bit later..

Attempted to use Gypsy this morning with a custom field which uses Mark Hout’s File extension as the field type. The custom field showed up on all publish pages despite being configured to only appear on one. Is this a known incompatibility or something which I might be doing incorrectly?

mr_dimsum - 23 April 2009 04:45 AM

Just wanted to add: Has anybody tried using Gypsy in an SAEF? Get Satisfaction doesn’t seem to have any answers to this question for 2 months. Will be giving it a go a bit later..

I thought I’d chime in just case you don’t have a solution yet.

I have a simple SAEF here -

What you have to do is first of all define the weblog name then in the custom fields group you have the Gypsy field in, hover over and in your status bar at the bottom of the browser will be the a link and the bit at the end with the number is what you need to tack on the end of the field_id_ bit above (where I have written field_id_1 in this case).

By the way Brandon,

Search doesn’t seem to work with Gypsy :(

Bug alert! Email/URL obscuring settings are not being honored in related_entries with Gypsy…

How I found it…I had shut off all “Automatically turn URLs and email addresses into links?” in my weblogs, every single one.

I iterate out one weblog into my template, which has a Gypsy text field I store an email in, which comes out fine as text instead of obscuring script. I then use {related_entries id=“customfieldhere”} to find a related entry to that field. It is slipping into obscuring the email for that related entry despite the fact that the parent AND the child are both set to not do so.

I unset this field as a Gypsy field and then it works fine. So the bug, unfortunately, is Gypsy.

Not a killer on this project (as the field group is assigned to both weblogs that need the field, so when they share a field I can just default to it not being Gypsy) but something maybe to look at fixing, none the less.

You should let Brandon know in his GetSatisfaction.com page, I’m not sure how often he checks this.

I tried, it needed an account to post, and it was 1am or so and I was too damn tired to create a new account that I’ll soon forget I have. LOL