Same problem as mentioned above #2
‘where’ => $where,
‘limit’ => 30,
‘orderby’ => ‘date DESC’
);
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
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 4 years, 6 months ago by
rinoxstudio.
-
This reply was modified 4 years, 6 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.
@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.
I’ll continue looking into the date alias issue in orderby and will get it resolved in Pods 2.8.2
@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.
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
Awesome, thanks for letting us know it also worked for you!
