Gypsy

Awesome this, will definitely try this out in a next project. Many thanks!

This just solved several serious headaches for me - title fields for multilingual sites for one…

Brilliant work Brandon!

-Brent

This does sound like a really excellent extension and one I am bound to use in the future. Good work Brandon!

I’m having a hard time getting Gypsy to work. I’ve uploaded both files and enabled the extension. Then I set a field to appear in all available weblogs (it’s a dev site) and the field is not appearing.

Have I missed a step?

How do I debug from here?

I’m having a hard time getting Gypsy to work. I’ve uploaded both files and enabled the extension. Then I set a field to appear in all available weblogs (it’s a dev site) and the field is not appearing. Have I missed a step? How do I debug from here?

Do you have EE 1.6.5, build 20081031 or later?

Ahh, versions… guess those matter, eh?

Thanks for the help Brandon

I could definitely make use of this like…right now. My only fear with modules and extensions now (and I use a lot) is that with 2.0 coming, what features will be now built in? Or will the new codebase render some modules too difficult to refactor?

Haha, I read about this extension a few days ago and think, “hmm, how useful this will be I’m sure.” Then during a functionality addition to a previous project (yay for getting paid on old projects!) I encounter the concept that I need two parallel couplets of weblogs wherein the only difference is that there’s a relationship field - the first weblog needs to relate to its pair (a main page/sub page structure), the other to its own pair, and all of it needs to show up in the menu/submenu structure with an or (|) call to the weblog name. I wanted to reuse the fields because good lord, I do NOT need another “if weblog_short_name==mainpage2 then output the same exact page as mainpage1 but with the field names changed”…what a headache that is (to maintain and to add code to later on). Or if or or if or if or. Ack!

However, with the Gypsy fields (nifty name BTW!) as relationship fields, I can have one set have the one related field, and the second set have the other, and never the twain shall interfere, but use the same fields for every other godforsaken part of the weblog, and reuse the output code in the same template. Wheeeeeeeeeee!

Thanks! Of course, now I have to update the site to the 1.6.6 version (from 1.6.4) but I was sorta planning on it anyway…

Hi. I was accidentally running this is PHP4 and got this error [error] [client 86.44.93.18] PHP Parse error: syntax error, unexpected ‘(‘, expecting ‘}’ in /path_to/extensions/ext.gypsy.php on line 486

Switched over to PHP5 and was fine.

Thanks for the extension

I was accidentally running this is PHP4 and got this error [error] [client 86.44.93.18] PHP Parse error: syntax error, unexpected ‘(‘, expecting ‘}’ in /path_to/extensions/ext.gypsy.php on line 486 Switched over to PHP5 and was fine.

Thanks for the bug report. Any chance you’d like to accidentally change it back to PHP4, and test an updated version to see if I’ve fixed it? If so, PM me your email address.

-Brandon

That PHP 4 bug has been sorted out in Gypsy 1.0.2: http://brandon-kelly.com/apps/gypsy

Many thanks to Brendan for telling me about the issue and beta testing the fix.

Hi Brandon,

Another great idea for an extension, I think this is how the custom fields should work out-of-the-box.

I’m afraid for me enabling the extension is causing an error message when clicking to publish new or edit existing entries:

Fatal error: Call to undefined method Extensions::call_extensions() in /www/[snip]/public_html/[snip]/cp/cp.publish.php on line 662

The installation is running MSM, v.1.6.5 Build: 20081031 and it’s on php 5.1.6.

Is this an MSM issue perhaps?

James

I’m afraid for me enabling the extension is causing an error message when clicking to publish new or edit existing entries:

Fatal error: Call to undefined method Extensions::call_extensions() in /www/[snip]/public_html/[snip]/cp/cp.publish.php on line 662

That sounds more like an issue with your EE install. Are you running any other extensions successfully?

Hiya Brandon,

Yes I’m running several other extensions successfully. When I disable Gypsy the error goes away. Feel free to have a look if you like - it’s the same installation and login that I created for you a few days ago for the issue I’m having with the Editor extension.

James