2.8 Update problems

  • Resolved rinoxstudio

    (@rinoxstudio)


    3 years, 4 months ago

    After last update there are some problems with Custom fields and looping via pods()
    1. Incorrect fields work. For example
    – date fields show nothing to pick, empty dropdown
    – relationship fields whith list view autocomplete lost drag’n’drop
    – wysiwyg looses next lines, updating existing posts stucks all texts in one paragraph.
    When I open post editor wysiwyg fields ignore existing “next lines” and updating makes every text as one paragraph on fornt-end.

    2. Looping. Orderby “date DESC” doesn’t work, posts just ordered by post_title.

    $params = array(
    ‘limit’ = 300,
    ‘orderby’ = ‘date DESC’
    );
    pods(‘services’,$params);

Viewing 12 replies - 1 through 12 (of 12 total)

  • Same problem as mentioned above #2

    $params = array(
    ‘where’ => $where,
    ‘limit’ => 30,
    ‘orderby’ => ‘date DESC’
    );

    Plugin Contributor Scott Kingsley Clark

    (@sc0ttkclark)

    1. For the date field, I can’t reproduce what you’re talking about here, can you post more details about that specific problem to our GitHub at https://pods.io/submit/
    2. I’ve reported the sorting issue with autocomplete here: https://github.com/pods-framework/pods/issues/6206 — we’ll get to working on a fix for this in an upcoming release this month.
    3. What are you seeing here, it’s trimming the extra lines at the start/end of the content? Or are you saying it’s removing extra lines within the content like taking 2-3 linebreaks and removing all of them? Can you post more details about that specific problem to our GitHub at https://pods.io/submit/
    4. The issue with orderby date DESC should technically be fixed by Pods 2.8.1 which is about to go out in a minute. When it goes out, can you please verify it addresses your problem? The correct orderby usage is actually t.post_date DESC for that field based on Documentation here: https://docs.pods.io/code/pods/find/find-reference-table/
    Thread Starter rinoxstudio

    (@rinoxstudio)

    1. The problem is with date format. For examle setting format as 21.10.2021 crashes dropdown. And date data stored in old versions and displayed with new date field in this format has not native look, seems like straight DB value. 2022-01-24T00:00:00+03:00
    2. Thanks
    3. New WYSISYG field removes new lines within the content. I suppose the reason is ignoring “next line” symbols of old editor strored in db. If we go next line in old wysiwyg editor on “text” tab and swap to visual tab we had next lines in text without any additional tags wrapping our content. But now when you set next lines in text tab, then turning back to visual – all next lines ignores. The same thing with the data already stored in db. It stores whith a specific symbol to make next line, but new editor ignores it and stucks lines together. New editor makes new lines only with setting </br> tag by clicking shift + enter in visual editor and ignores old format of next lines.
    4. now it works with t.post_date DESC, thanks

    One more problem on test copy of only one of the sites:
    5. Pods editor. Pods -> Edit Pod -> Pod throws me this

    Notice: Trying to get property 'ID' of non-object in /var/www/u1432973/data/www/test.vshp.pro/wp-includes/post.php on line 7333

Notice: Trying to get property 'ID' of non-object in /var/www/u1432973/data/www/test.vshp.pro/wp-includes/post.php on line 7334

Notice: Trying to get property 'ID' of non-object in /var/www/u1432973/data/www/test.vshp.pro/wp-includes/post.php on line 7334

Notice: Trying to get property 'ID' of non-object in /var/www/u1432973/data/www/test.vshp.pro/wp-includes/post.php on line 7345

Notice: Trying to get property 'post_type' of non-object in /var/www/u1432973/data/www/test.vshp.pro/wp-includes/post.php on line 7353

    ….. and so on

    Thread Starter rinoxstudio

    (@rinoxstudio)

    3. Just looked to DB, and it’s real. All “next lines” were stored in DB as \r\n by old WYSIWYG editor. New editor ignores \r\n and we have stucked paragraphs instead.
    5. and if I turn off debug mode site throws 502 Bad Gateway from Apache sometimes or

    Warning: Invalid argument supplied for foreach() in /var/www/u1432973/data/www/test.vshp.pro/wp-content/plugins/pods/classes/PodsAPI.php on line 310

    Warning: Invalid argument supplied for foreach() in /var/www/u1432973/data/www/test.vshp.pro/wp-content/plugins/pods/classes/PodsAPI.php on line 357
    Cannot save group to collection

    • This reply was modified 3 years, 4 months ago by rinoxstudio.
    • This reply was modified 3 years, 4 months ago by rinoxstudio.

    For me the problem with orderby still exists within 2.8.1
    I use the Gutenberg block “Pods List-Items”.

    About date DESC.
    Upgrading to 2.8.1 doesn’t look fixing the problem.
    After changing the code like

    $params = array(
    'where' => $where,
    'limit' => 3,
    'orderby' => 't.post_date DESC'
);

    it went good.
    Thank you for the suggestions.

    Plugin Contributor Scott Kingsley Clark

    (@sc0ttkclark)

    @rinoxstudio Regarding the new lines and the editor, are you using the new Quill editor? Unfortunately it does not support <br> tags and it only supports <p> output. Our team is finding some workarounds for this but for now your best bet is to continue to use TinyMCE if you need support for <br> line breaks.

    Plugin Contributor Scott Kingsley Clark

    (@sc0ttkclark)

    I’ll continue looking into the date alias issue in orderby and will get it resolved in Pods 2.8.2

    Thread Starter rinoxstudio

    (@rinoxstudio)

    @sc0ttkclark I am using Tiny MCE. Before 2.8 line breaks in WYSIWYG field were stored in database with \r\n symbols, after 2.8 update WYSIWYG field ignores \r\n and stucks lines together.

    Thread Starter rinoxstudio

    (@rinoxstudio)

    Problem with line breakes seems to be fixed in 2.8.2. Thank you.

    The date/orderby problem is solved with 2.8.2. Thank you

    Plugin Author Jory Hogeveen

    (@keraweb)

    Awesome, thanks for letting us know it also worked for you!

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘2.8 Update problems’ is closed to new replies.

Tags