Playa

Hi Brandon,

I think I have conflict between Playa and other extensions. Currently, it breaks the “choose field type” dropdown, so nothing works there.

Here are my extensions:

Edit Tab AJAX
Admin Section With Tabs! Edit Menu (v.1.0) Gallery dropdown (v.1.0.0)
LG Add Sitename (v.1.0.1)
LG File Manager (v.1.2.0) LG Better Meta (v.1.4.0) LG TinyMCE Custom Field (v.1.1.5) URL Field Extension (v.1.0.2) Playa (v.1.0.9)

I also have Mark Huot’s checkbox extension, but I disabled that.

See any glaring problems?

Thx,

Ben

Hey Guys

Just found bug on the dev server I am using with the Playa extension. When developing on a server with no domain live (say http://srv1.example.com/~customername), the line 603

$playa_dir = '/'.$PREFS->ini('system_folder').'/extensions/playa/';

Will always lead to problems and not include the js and css scripts, because it will try to include it from

http://srv1.example.com/system_folder …

instead of the appropriate folder appended.

I fixed this by slightly changing the Playa extension and adding the site url which can be controlled from the CP.

My proposal:

$playa_dir = $PREFS->core_ini['site_url'].$PREFS->core_ini['system_folder'].'/extensions/playa/';

Other than that, wonderful extension!

Great extension.. Have finally put it to use and simply love it. Would be great if this can work with galleries in the short future. =)

Cheers, D.

It appears LG Tiny MCE extension does not play nice with Playa.

Here is my workaround, for now:

• Copy your LG Tiny MCE settings in to Notepad, and save. Then disable the extension.
• Enable Playa
• Create your Playa fields
• Now enable LG Tiny MCE and paste the settings back in.

It works fine, but if you need to make more Playa fields, I think you’ll need to repeat these steps.

-Ben

Brandon,

Thanks for the wonderful plugin.

In an earlier post you had mentioned adding an option to show more than just “open” statuses. Until that option is added, could you (or anyone else) point me in the right direction towards modifying the plugin to display certain statuses? Even showing all statuses would be better for my situation than showing just open.

Thanks, Brian

Several additional features would make this a killer. - Ability to search titles (helpful when there are hundreds or thousands of entries and you already know a word in the title)* - Ability to choose categories* *The first two functions can be seen in the Selected Items module, screen shot attached. Keep up the great work!

I’m telling you, if there was a mash-up between Selected Items and Playa, it would be a real winner. I find Selected Items useful, but almost impossible to implement every time - mostly due to the fact I like to use a masked control panel. If Selected Items’ interface was as slick as Playa’s, and was as easy to implement as Playa, I can see a real demand for that.

I’m thinking of making a weblog with one entry called “Custom Orders” and a number of custom fields (as many as I need) that are all Playa fields - and essentially doing what Selected Items does.

I’m encountering an error with this module through the system folder masking procedure located in the documentation here.

When I access one of my sites (from MSM) through its own independent admin.php file located on its domain, whenever I want to Publish or Edit entries, the module goes haywire. Seems like it’s not picking up the js.

Picking up from a post above from Kevin, I’ve checked the source and here’s the details:

<link rel="stylesheet" type="text/css" href="/system/extensions/playa/playa.css?v=1.0.9" />

var playa_dir = "/system/extensions/playa/";

I’m guessing this problem stems from a path.php parameter I have set, but not entirely sure:

"$cp_url = 'http://example.com/admin.php';

UPDATE: Seems even if I remove the setting specified above in path.php, the problem persists. Also verified my system folder was pointed correctly in the config.php file as well.

Great module!

For some reason I’m getting this error when I load the index of a template group.

Notice: Undefined index: game in /.../.../.../.../.../extensions/ext.playa.php on line 1109

Notice: Undefined index: field_id_ in /.../.../.../.../.../extensions/ext.playa.php on line 1119

The same error repeats itself like a hundred times, and then loads the page.

On the page I want to load, this is the code.

{embed="global/main_header" entry_id="{entry_id}"}
<div id="main-content">
<div id="leftcolumn">
{embed="modulos/analisis_recientes"}
{embed="modulos/lista_analisis"}
</div>
{embed="global/sidebar"}
</div>
{embed="global/main_footer"}

In {embed="modulos/analisis_recientes"} I have:

{exp:weblog:entries weblog="review" disable="categories|member_data|trackbacks" limit="1" paginate="top" sort="desc" rdf="off"}
<div class="modulo" id="AnalisisRecientes">
    <div class="moduloCabezera">
        <h2>Análisis Más Reciente</h2>
    </div>
    <div class="moduloCabezeraSub">
        <span>Recién salido del horno para vosotros.</span>
    </div>
    <div class="moduloGameBanner">
    {related_entries id="review_game"}
    {embed="modulos/GameBanner" the_id="{entry_id}"}
    {/related_entries}
    </div>
    <div class="moduloContenido">
        <h3>//{title}</h3>
        <span class="BodySubtitle">{review_subtitle}</span>
        {exp:word_limit total="100"}
        {review_body}
        {/exp:word_limit} 
    </div>
</div>
{/exp:weblog:entries}

In {embed="modulos/lista_analisis"} I have:

<div class="modulo" id="ListaAnalisis">
    <div class="moduloCabezera">
        <h2>Lista de Análisis</h2>
    </div>
    <div class="moduloCabezeraSub">
        <span>Todos nuestros análisis a fondo.</span>
    </div>
    <div class="moduloContenido">
        <table>
            <tbody>
                <tr>
                    <th id="thumbnail"></th>
                    <th id="title">Juego</th>
                    <th id="genre">Nota</th>
                </tr>
                {exp:weblog:entries weblog="review" disable="categories|member_data|trackbacks" limit="10" paginate="top" sort="desc" rdf="off" offset="1"}
                <tr>
                    <td headers="thumbnail" align="center">{site_url}uploads/images/ps3/call_of_duty_4_modern_warfare/screenshot005_23052008_small.jpg</td>
                    <td headers="title">
                        <a href="http://{title_permalink=" title="Leer el análisis de {related_entries id="><h4 class="ListTitle">{related_entries id="review_game"}{title}{/related_entries}</h4></a>
                        <span class="ListSubtitle">{review_subtitle}</span>
                        
                        {exp:eexcerpt if_exceeds="25" stop_after="20"}
                        {review_body}
                        {/exp:eexcerpt}
                        
                    </td>
                    <td headers="genre" align="center"><h4 class="ListScore">{review_score}</h4></td>
                </tr>
                {paginate}
                Página {current_page} de {total_pages} - {pagination_links}
                {/paginate}
                {/exp:weblog:entries}
            </tbody>
        </table>
    </div>
</div>

And in {embed="global/sidebar"} I have:

<div id="rightcolumn">
{embed="modulos/panel_de_usuario"}
{embed="main_site/module_toptengames"}
<div class="modulo">
    <div class="moduloCabezera">
        <h2>Comunidad</h2>
    </div>
    <div class="moduloCabezeraSub">
        <span>Intercambia tus opiniones con el resto.</span>
    </div>
    <div class="moduloContenido" id="AnuncioSidebarForo">
        <a href="http://{site_url}index.php/foro/" title="Ven a la comunidad">{site_url}images/interface/unete-a-los-foros.jpg</a>
    </div>
</div>
{embed="modulos/publicidad_sidebar"}
</div>

I have no idea on why that error is being displayed. :S

When I access one of my sites (from MSM) through its own independent admin.php file located on its domain, whenever I want to Publish or Edit entries, the module goes haywire. Seems like it’s not picking up the js.

I would just hardcode the path to the JS and CSS files in the extension if I were using Playa in a MSM situation. One way or the other, you’re probably going to have to modify the Playa extension file directly.

I always mask my CP, and doing this small tweak (listed above) helps fix the path issue - at least on a non-MSM setup.

Just wanted to ask again: Does anyone knows how to modify the code to return ALL statuses with related_entries instead of just Open? Thanks!

Brian

I would just hardcode the path to the JS and CSS files in the extension if I were using Playa in a MSM situation. One way or the other, you’re probably going to have to modify the Playa extension file directly. I always mask my CP, and doing this small tweak (listed above) helps fix the path issue - at least on a non-MSM setup.

The tweak does not work in MSM environments unfortunately. The site_url may be correct for specifying the MSM site_url, but the system folder is located elsewhere. I had to just hardcore the link, as you suggested to get this to work. Hopefully a fix for this comes about, but the extension is good enough to validate using even without it.

Dying to use this one, looks great and solves a few challenges we’ve been having.

Our server is running php4, but with the hack, it works well. BUT, when TinyMCE extension is enabled, the Playa CSS and JS refuse to load.

I’ve tried 4midori’s suggestions above, but once I re-enable TinyMCE, the Playa fields stop working once again (no JS or CSS when I view source).

Any idea what is causing the conflict between the two extensions?

tx!

UPDATE: It’s working! Thanks to slapshotw’s earlier post, where he had a conflict with the TEH extension, I manually changed the priority level of Playa’s “publish_form_headers” entry in the exp_extensions table to 11. Working well with the TinyMCE extension now.

Somehow the PHP notice messages that I was talking about on my previous post have been resolved. I’m not 100% sure on why they were appearing, but I could be because I was using the Multi-Relationship extension, and then uninstalled it converting the specific custom field back to a normal relationship one.

Anyway, they have gone now. Wierd.

UPDATE: It’s working! Thanks to slapshotw’s earlier post, where he had a conflict with the TEH extension, I manually changed the priority level of Playa’s “publish_form_headers” entry in the exp_extensions table to 11. Working well with the TinyMCE extension now.

@ira42: Thanks for posting that…I had totally missed that, and was wondering how I could get TEH and Playa to ever work together. Apparently they do with that small tweak. Made my day! These long forum threads make it a little tough to find relevant info after a while.