Playa

Brilliant idea about disabling the Quick Save button if a change has been made to the Playa field.

Ditto! And thanks for the work with TEH, Ryan.

And thanks for the work with TEH, Ryan.

I didn’t do much - but I might have helped narrow down the issue, at least. I use TEH on every build, so I’d love to ensure that it’s as compatible as possible with other Extensions.

UPDATE: I give up. I tried everything I could think of with my limited knowledge. I have some money burning a hole in my PayPal account for anyone who can get Textile Editor Helper to not hose all of Playa’s JS.

Thanks for the note about the system_folder, Ryan. It’ll get added in the next version.

The problem with TEH lies with Prototype, a javascript library that gets included by extension. The fix would require several forks in Playa’s JS code, to handle things differently if Prototype is present.

I thought there was an issue with Prototype. Shoot. TEH is a handy extenion, and I have a request over at the TEH thread asking if someone can make a jQuery version.

I actually found a slicker looking jQuery-based script for this sort of thing called markitup - which would make for one cool custom field type - and I’m sure with the esay-to implement no-conflict mode in jQuery, this could be made to play nice not only with Playa, but other scripts as well.

I’ll figure something out. Thanks, Brandon!

For the record, I just did a test install, and whipped together an Extension for a Markitup custom field…and Playa and Markitup both play very nice together.

It isn’t ready for prime time, but it works and if I can polish it a bit, I may release it.

Hi Guys:

I assume it’s easily solved, but I’m not seeing the Playa panel in my publish page. I see a wonderful unordered list, and also have a JS error:

playa_init is not defined
playa_init("9", 3);

It’s a new installation of EE, and I have only GeoCoordinates installed (I’ve disabled and re-enabled that). I’ve tried viewing the publish page in EE and FireFox, but with no change.

Does anyone have any suggestions?

Regards

Ben

Does it work when the other extension is disabled (without re-enabling it)?

Yes – I should have been more explicit: I disabled Geo-Coordinates, tried Playa again and got the same results before re-enabling it. Here’s what else I’ve done…

1. Checked that the JS file is reachable and in the directory structure
2. Checked that playa_init is in there (!)

One dumb question, should the line below include my site URL?

script type="text/javascript" src="/system/extensions/playa/playa.js?v=1.0.9"

Thanks for the quick response.

Ben

One dumb question, should the line below include my site URL?

script type="text/javascript" src="/system/extensions/playa/playa.js?v=1.0.9"

No, beginning a URL with a slash (/) is effectively the same thing as typing the domain name in.

Hi all

I’ve a question regarding Playa. Please take a look at my thread here. I’m approaching the pull-my-hair-out stage with this one!

Just to update the thread…the odd behaviour (seeing a UL and a JavaScript error) is my error during installation of EE.

Brandon suggested –

Open your config.php file and make sure that $conf[’system_folder’] is set to the correct path to your system folder.

This worked and I now see the UI as I should. Thanks, Brandon, for your help here.

Sincerely

Ben

Was wondering if there were any developments on this using the backspace parameter? I’m not PHP expert, can handle basic scripting, but would just generally like to avoid it at all costs as a personal preference.

I can’t get the javacript to load! :shut:

At first I thought it was because of TinyMCE, but I’ve disabled every single extension and it still doesn’t work.

On a side note, I was wondering if ths extension could help me with this problem over here.

On the Edit page, View Source and search for “playa.js” or “playa.css”. Verify that the include path for those files is correct. If it’s not, please open your system/config.php file and make sure that $conf[’system_folder’] is set to the correct path to your system folder.