Johann Heyne

If ‘table’ is in your group field, you have to get the table like this…

$zone_4 = get_field('zone_4');
$table = $zone_4['table'];

Hi,

thanks for the request. I add this feature to version 1.2.

Cheers,
Johann

Hello Edir,

thanks a lot for your feedback, I appreciate that very much.

All your points are on my list.

Coping existing tables of other posts is a good idea. I will try to find a smart solution.

The tooltip interface was born because it was the most stable implementation to start with. But you are right. There must be several types of content. At this point I have simple text and the WordPress editor (pre-definable button sets for the editor is planed). But this content types list is open to be extended with others and appropriate input tools. Even validating and calculation functionality is a point I think about. But this is not to expect for the first release.

If have implemented field settings for optional providing styles (CSS-classes) to select for the whole table, columns, rows and cells. So this is an unlimited solution for providing styling options.

It is right now possible to predefine a table and its content in the field setting with the same table editor for editing tables. There will be also a way to delimit almost functionalities in the field settings for editing a table.

Cheers
Johann

Sorry, but you cant´t yet. Im working on a Pro version with a lot of features like predefining a table. The launch is expected in spring 2018.

The code example to get a table field´s data and rendering the table has to be placed in a template. The ACF field must, of course, be available for this template.

Hi, after some testing, I did not found a situation, that replicates that issue. Is there a way to get my hands on your project to investigate the issue?

Thanks,
Johann

Hi,

I´m not into this template engine, but in some way it should work like…

<?php

    echo $twig->render( 'template.html', array( 'table' => get_field( 'my_table_field' ) ) );

template.html…

{% if table|length > 0 %}

    <table>
    
        % if table.header|length > 0 %}
            <thead>
                <tr>
                    {% for header in table.header %}
                        <th>{{ header.c }}</th>
                    {% endfor %}
                </tr>
            </thead>
        {% endif %}

        % if table.body|length > 0 %}
            <tbody>
            {% for row in table.body %}
                <tr>
                    {% for cell in row %}
                        <td>{{ cell.c }}</td>
                    {% endfor %}
                </tr>
            {% endfor %}
            </tbody>
        {% endif %}
    
    </table>
    
{% endif %}

• This reply was modified 9 years, 3 months ago by Johann Heyne.
• This reply was modified 9 years, 3 months ago by Johann Heyne.
• This reply was modified 9 years, 3 months ago by Johann Heyne.

Hello torbent,

I´m sorry, but at the moment, there is no other solution than having this blue editing box.

Greetings,
Johann