Gypsy

I have no idea how this happened and whether it was my fault or whether it was a bug in 1.6.5 but line 662 in that file (cp.publish.php) had the method call_extensions() when it should have been call_extension(). Changing that worked.

And that didn’t break everything else?

nope, all’s well I think… just delving into the extension now

Is the extension SAEF compatible? I.e. will I be able to use ‘gypsy’ fileds in my Stand-alone antry form without hard-coding them?

Is the extension SAEF compatible? I.e. will I be able to use ‘gypsy’ fileds in my Stand-alone antry form without hard-coding them?

Unfortunately, the hook that Gypsy hangs on doesn’t get called by SAEF :(

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!

I’ve noticed that if you are using Gypsy for your fields and then hit update on an entry the fields/content doesn’t appear (ie only non-gypsy fields appear). I’d like to see this fixed in a future version. Otherwise nice extension!

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:

Notice: Undefined index: field_is_gypsy in /extensions/ext.gypsy.php on line 516

Notice: Undefined index: gypsy_weblogs in /extensions/ext.gypsy.php on line 518

Warning: session_start() [function.session-start]: Cannot send session cache limiter - headers already sent (output started at /extensions/ext.gypsy.php:516) in /extensions/ext.lg_htaccess_generator_ext.php on line 672

Any ideas?

Cheers, Kippi

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

Notice: Undefined index: field_is_gypsy in /extensions/ext.gypsy.php on line 516

Notice: Undefined index: gypsy_weblogs in /extensions/ext.gypsy.php on line 518

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

Any clues?

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

@tilzinger LOL

It was a stressful morning 😊

Great extension btw.