coding-panda / panda-pods-repeater-field Goto Github PK

Created Repeater Field Group following both video and picture instructions. But there's nothing in More Fields section on post page editor. Deactivated all plugins besides Pods and Panda, and am using Wordpress' default theme - same thing. Did I miss something?

System:
Wordpress 6.3.1
PHP 8.2.10
Pods: 3.0.4
Panda Pods: 1.5.11

Hi,

Thank you for the nice plugin. I was testing Pods 2.9 alpha and the simple repeatable fields work nicely. Beta will release in next few days. I understand your plugin right now uses ACT to store values and link with cpt to show them on the front-end. But now we will have simple repeatable fields and not nested in the core. What will be the approach post 2.9 release?

Best regards,

Hi, could you, please, merge #7 to fix incorrect handling of WP Object Cache? Thank you.

I've created a set of repeater fields for one of my pod.
The repeater field is a WYSIWYG field. I use TinyMCE editor for this wysiwyg field.
Everything works fine except the wysiwyg editor loses all the html/alignment done in the editor.
Other non-repeater wysiwyg editor field in mypod works just fine.

Steps to reproduce

1. Create a ACT - paragraph
2. create a field column_one, select type as WYSIWYG (Visual Editor)
3. Save the ACT
4. In the pod (say article), crete a new field paragraph
5. select Panda pod repeater field as type of the field
6. select the 'paragraph' ACT in the Pods Table field under additional field options tab.
7. Add a new itemto article pods
8. type some content inside the paragraph repeater field and make some html changes like bold, italics, line break etc.
9. save the repeater field
10. open the repeater field again.

Expected behaviour:

1. The visual editor should retain the bold, italics and line breaks

Actual Behaviour:

1. The visual editor loses all the html changes and has a blob of text.

note: tested on Mozila Firefox 88.0.1 on Ubuntu 18.01 LTS

Hi again,

I am hoping you can help me with this solution considering your experience. I am looking to find out a scalable solution for lots of content. I need repeater fields.

1. Using Pods with Table Storage Type Custom Fields & Your ACT Solution.

2. Using Metabox with table based custom fields and normal cpt.

3. ACF with repeater with local json file and may be this plugin. https://wordpress.org/plugins/acf-to-custom-database-tables/

4. Converting the data to Post Data. But then I will lose the flexibility to filter specific data from the post.

What will be the most performant solution?

Hi there,

I just got this error in the frontend and obviously it seems an instance of live has escaped in admin.js line 647.

By the way, is admin.js something that should be loading in the frontend and not just in the backend?

Thank you for your work!

Hey there!

I have the latest version of Panda and the latest version of PODS!

When I try to add a repeater field, it didn't show up. After some debugging I found that your plugin wasn't creating the fields "pandarf_created" and "pandarf_modified" properly!

Could you check this and possibly fix it?

After I created the fields manually directly into the database, everything got running no problem :)

Hi,

Problem

I am using panda-pods-repeater-field with pods framework.

Following is my structure:
Section -< SectionList

Inside the setting, I have defined SectionList as one of the repeated field in Section.

However, when I retrieve the data using rest api. Every section has the same section list.

In admin page, it suppose to have the different section list.
Record 1: What we do

Record 2: What will you get

Expected output

When retrieve data using REST API, it should return the correct array as shown in the admin page.

Hi,

I can't get this working. How do you get a relationship field from a repeater? Let's take for example a relationship product category taxonomy.

Hi again,

I was wondering if there is any tool to convert ACF Repeater / Metabox Cloneable Group Data into Pods with ACT like yours plugin or vice versa? I am wondering what are my options if I decide to migrate out of Pods or use it for an existing ACF / metabox site.