What other extensions do you have enabled? I have playa working on 1.6.3 perfectly. Try disabling other extensions and 3rd party plugins and see what you get.
Thanks, I’ve tried disabling all my extensions and no dice. The only plugins I have installed are the default plugins you get with a clean install.
I’ve also checked the path to my system folder, which is fine, Playa js and css are both being called without a hitch.
Can anybody give me any clues here at all? I just upgraded to 1.6.4 and I’m still having exactly the same problem - I can’t edit my custom fields whilst Playa is enabled.
I am running PHP 5.2, I have tried disabling all extensions with no luck. I have no weird plugins or modules installed whatsoever.
I am totally mystified.. could this be a server setting with my host? Please help! I need multi-relationships to build my project.
Ok, after much messing about with my testing server and reinstalls etc I have found that the extension fails as soon as you have more than 19 weblogs that share the same custom field group.
As soon as you assign a different custom field group to the 20th weblog, you are able to edit your custom fields again.
Brandon, can you shed any light on this at all? I was trying not to use categories, which is why I have so many weblogs sharing the same field group..
Can anybody tell me if this is generally a bad idea, and if this problem of not being able to edit fields is a bug with Playa, or some kind of mechanism to save the system from overload?
Ok, after much messing about with my testing server and reinstalls etc I have found that the extension fails as soon as you have more than 19 weblogs that share the same custom field group. As soon as you assign a different custom field group to the 20th weblog, you are able to edit your custom fields again.
Sounds like a memory issue… Try boosting PHP’s memory limit.
Thanks Brandon, though I’m not sure about that.
I’ve had exactly the same scenario on both my local Apache server and my shared hosting server. The shared hosting space has double the memory of my local server (although I’ll be the first to admit I don’t know much about how much memory to allocate to PHP).
Also, with debugging turned on there are no php errors coming through.. just no output at all where you should see the “edit custom field” form.
Anyhow, I’ve got Playa working now and tidied up my weblog and category structure at the same time, so all good. Thanks for the awesome extension, it’s just what I needed and I never did get Mark’s one to work despite trying all the fixes and upgrading PHP.
Sorry all for my lack of involvement on the forum lately. I’ve moved and started a new job in the last couple months, and life has been pretty crazy. Much thanks to all of you for helping each other out with the extension in my absence!
Going forward, it’s not going to be as easy for me to work on Playa, given that I’m no longer working at Design Reactor. BUT I’ve got a big list of things I want to do with the extension (custom status support, MSM support, and a Spotlight-esque filter to name a few). If you are an EE extension developer and would like to help out, get in touch with me! You can also contribute by sending me a donation on PayPal to brandon [dot] kelly [at] mac [dot] com. (Your money will go toward a good cause–I’ll donate the first $199 to Apple! :-)
I’ve had exactly the same scenario on both my local Apache server and my shared hosting server. The shared hosting space has double the memory of my local server (although I’ll be the first to admit I don’t know much about how much memory to allocate to PHP). Also, with debugging turned on there are no php errors coming through.. just no output at all where you should see the “edit custom field” form.
It still could easily by a PHP memory limit problem. PHP’s memory is set via its configuration and can usually be overridden in a PHP.ini file. It has little to do with actual server memory. I’ve seen PHP run out of memory and just stop parsing–no exception or error thrown. Have you tried increasing the php memory using php.ini? Something like memory_limit = 32M or 40M may work well.
Have you tried increasing the php memory using php.ini? Something like memory_limit = 32M or 40M may work well.
Nope, I haven’t tried that, I’ll give it a bash, thanks very much.. although as I say things seem to be working now.. is the fact that I need to increase the memory for php not a sign that there is an issue with my weblog structure?
Hi Brandon,
The Playa extension is a phenomenal help. I only just discovered it a few weeks ago and it’s being used throughout this project.
I apologize for not reading the full thread to see if this has been otherwise addressed, but as is most often the case, I’m scrambling on a few fronts with an error popping up.
It seems apostrophes in the titles of related content aren’t actually supported. I’ve spent a few minutes trying to edit the str_replace on the Update statement to no avail. Here’s what I’m getting:
MySQL ERROR:
Error Number: 1064
Description: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 's Clinics\r[852] Powder Clinics\r[853] Trees Clinics\r[!854] Racing / NASTAR Cli' at line 2
Query: UPDATE exp_weblog_data SET field_id_60 = '[851] Women's Clinics\r[852] Powder Clinics\r[853] Trees Clinics\r[!854] Racing / NASTAR Clinics\r[855] Private Lessons' WHERE entry_id = 23
Any help would be appreciated. I’m using the latest version downloaded from your site.
Thanks, Mark
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.