Ghost entries

Hi,

after upgrading my contao version from 2.7 to 2.8.4 and my catalog to 0.3.6 build 25 (and all the related modules are updated too) I have some sort of "ghost entries" in the catalog fields listing (please see attached screen).

These entries are only visible, if "show all" is selected, if I limit the view f.ex from 1-30 the ghost entries will disappear.
You also cannot delete these entries, because they do not have an ID. I've checked database and here everything is fine and each entry has an pid.

I also have done a "repair" already, but nothing changed. Catalog itself is working properly in the front- and backend, so it would be great to find a solution how to vanish these ghost entries.

Any help would be highly appreciated.

Kind regards,
Sares

Re: Ghost entries

Have you tried to delete them, because listing, editing, deleting and all move/cut/copy operations are all Contao functions.

Re: Ghost entries

I've seen this too, not in Catalog but in some modules I made.
I assumed it was a glitch in my modules as they were all 1:4:4 (Thyon will know what that means) and already have other "problems" inherent with this way of configing a module.
However, as I know Thyon doesn't make modules this way I now think it is a bug in the way Contao views all records.
It first appeared with Typolight 2.8, and it seems when you select "show-all" only the first half of the records are shown, and these are interspersed with the same amount of "blank" records.
It would help Sares if you could turn debugging on, and post the info that is printed out when you view all... it may shed some light on it.

Re: Ghost entries

well since 2.9, it seems we can make 1:4:4:4:4:N.... the Themes system is 1:4:4 already Theme=>Stylesheet => Style and that works correctly.

Re: Ghost entries

thats good news, hopefully when i update my modules will start redirecting on "save and go back" etc correctly...fingers crossed.

Re: Ghost entries

Hi Thyon,

Quote:

Originally Posted by thyon

Have you tried to delete them, because listing, editing, deleting and all move/cut/copy operations are all Contao functions.

yes, but it is not possible, because non of the entries do have an ID.
Please have a look at the following example:

Ghost entry:
http://www.meinedomain.com/typolight...s&act=edit&id=

normal entry:
http://www.meinedomain.com/typolight...act=edit&id=77

You can see, no id.
As told I have also taken a closer look at the database and there are only
46 entries in it and they all have pid and id, so there are no ghost entries
in the database...

Kind regards,
Sares

Re: Ghost entries

Hi Ramjet,

Quote:

Originally Posted by ramjet

It would help Sares if you could turn debugging on, and post the info that is printed out when you view all... it may shed some light on it.

thanks for your answer.

Please find attached the debug-information:

Code:

Array ( [0] => Array ( [0] => SELECT * FROM tl_session WHERE hash='fcb2afd349719542783c45ed63b50100a4356f65' AND name='BE_USER_AUTH' [1] => 1 rows returned [2] => Array ( [id] => 1 [select_type] => SIMPLE [table] => tl_session [type] => system [possible_keys] => hash [key] => [key_len] => [ref] => [rows] => 1 [Extra] => ) ) [1] => Array ( [0] => SELECT * FROM tl_user WHERE id='1' [1] => 1 rows returned [2] => Array ( [id] => 1 [select_type] => SIMPLE [table] => tl_user [type] => const [possible_keys] => PRIMARY [key] => PRIMARY [key_len] => 4 [ref] => const [rows] => 1 [Extra] => ) ) [2] => Array ( [0] => SELECT * FROM tl_user_group WHERE id=NULL AND disable!=1 AND (start='' OR start<1278926345) AND (stop='' OR stop>1278926345) LIMIT 0,1 [1] => 0 rows returned [2] => Array ( [id] => 1 [select_type] => SIMPLE [table] => [type] => [possible_keys] => [key] => [key_len] => [ref] => [rows] => [Extra] => Impossible WHERE noticed after reading const tables ) ) [3] => Array ( [0] => UPDATE tl_session SET tstamp=1278926345 WHERE sessionID='d28886f9b0bcc7f16ef54f561050b0c5' [1] => 1 rows affected ) [4] => Array ( [0] => SELECT * FROM tl_catalog_fields WHERE pid='2' ORDER BY sorting [1] => 46 rows returned [2] => Array ( [id] => 1 [select_type] => SIMPLE [table] => tl_catalog_fields [type] => ALL [possible_keys] => pid [key] => [key_len] => [ref] => [rows] => 35 [Extra] => Using where; Using filesort ) ) [5] => Array ( [0] => SHOW COLUMNS FROM `tl_taxonomy` [1] => 7 rows affected ) [6] => Array ( [0] => SELECT id, name FROM tl_taxonomy WHERE id IN (63,64,65,66,67) ORDER BY name [1] => 5 rows returned [2] => Array ( [id] => 1 [select_type] => SIMPLE [table] => tl_taxonomy [type] => range [possible_keys] => PRIMARY [key] => PRIMARY [key_len] => 4 [ref] => [rows] => 5 [Extra] => Using where; Using filesort ) ) [7] => Array ( [0] => SELECT id, name FROM tl_taxonomy WHERE id IN (6,7,8,9,10,11,12,13,14) ORDER BY name [1] => 9 rows returned [2] => Array ( [id] => 1 [select_type] => SIMPLE [table] => tl_taxonomy [type] => ALL [possible_keys] => PRIMARY [key] => [key_len] => [ref] => [rows] => 65 [Extra] => Using where; Using filesort ) ) [8] => Array ( [0] => SELECT id, name FROM tl_taxonomy WHERE id IN (77,78,79,80,81,82,83,84,85,86) ORDER BY name [1] => 10 rows returned [2] => Array ( [id] => 1 [select_type] => SIMPLE [table] => tl_taxonomy [type] => ALL [possible_keys] => PRIMARY [key] => [key_len] => [ref] => [rows] => 65 [Extra] => Using where; Using filesort ) ) [9] => Array ( [0] => SELECT id, name FROM tl_taxonomy WHERE id IN (74,75) ORDER BY name [1] => 2 rows returned [2] => Array ( [id] => 1 [select_type] => SIMPLE [table] => tl_taxonomy [type] => range [possible_keys] => PRIMARY [key] => PRIMARY [key_len] => 4 [ref] => [rows] => 2 [Extra] => Using where; Using filesort ) ) [10] => Array ( [0] => SELECT id, name FROM tl_taxonomy WHERE id IN (87,88,72,68,69,70,71,19,20,21,22,23,24,25,26,27,59) ORDER BY alias [1] => 17 rows returned [2] => Array ( [id] => 1 [select_type] => SIMPLE [table] => tl_taxonomy [type] => ALL [possible_keys] => PRIMARY [key] => [key_len] => [ref] => [rows] => 65 [Extra] => Using where; Using filesort ) ) [11] => Array ( [0] => UPDATE tl_catalog_types SET dca='REMOVED BECAUSE OF SECURITY' WHERE id='2' [1] => 0 rows affected ) [12] => Array ( [0] => DELETE FROM tl_catalog_fields WHERE id IN(1,2,3,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,49,50,51,52,76,77,78,79,80,81,82,83,84,85,86,87,88,89,90,91,100,101,104,105,106,107,108) AND tstamp=0 [1] => 0 rows affected ) [13] => Array ( [0] => DELETE FROM tl_catalog_fields WHERE NOT EXISTS (SELECT * FROM tl_catalog_types WHERE tl_catalog_fields.pid = tl_catalog_types.id) [1] => 0 rows affected ) [14] => Array ( [0] => SHOW COLUMNS FROM `tl_catalog_fields` [1] => 43 rows affected ) [15] => Array ( [0] => SELECT COUNT(*) AS total FROM tl_catalog_fields WHERE pid='2' [1] => 1 rows returned [2] => Array ( [id] => 1 [select_type] => SIMPLE [table] => tl_catalog_fields [type] => ref [possible_keys] => pid [key] => pid [key_len] => 4 [ref] => const [rows] => 45 [Extra] => Using index ) ) [16] => Array ( [0] => SELECT * FROM tl_catalog_types WHERE id='2' LIMIT 0,1 [1] => 1 rows returned [2] => Array ( [id] => 1 [select_type] => SIMPLE [table] => tl_catalog_types [type] => system [possible_keys] => PRIMARY [key] => [key_len] => [ref] => [rows] => 1 [Extra] => ) ) [17] => Array ( [0] => SELECT MAX(tstamp) AS tstamp FROM tl_catalog_fields WHERE pid='2' [1] => 1 rows returned [2] => Array ( [id] => 1 [select_type] => SIMPLE [table] => tl_catalog_fields [type] => ALL [possible_keys] => pid [key] => [key_len] => [ref] => [rows] => 35 [Extra] => Using where ) ) )

I only have edited the UPDATE statement, because there were sensible data in it.
Hopefully this is useful to find the problem.

Many thanks,
Sares

Re: Ghost entries

Heres my 11 records shown with "show all".... same....6 blank alternating with the first five 5 ok.
As Sares says you can't delete them, which is good as they are actual records... they just don't show.

[attachment=0:2agld5qv]ghost.jpg[/attachment:2agld5qv]

This is the debug info using show all....

Code:

Array ( [0] => Array ( [0] => SELECT * FROM tl_session WHERE hash='d14c5be9d8a482c376178a1e7a3d09ce4bb49fe2' AND name='BE_USER_AUTH' [1] => 1 rows returned [2] => Array ( [id] => 1 [select_type] => SIMPLE [table] => tl_session [type] => system [possible_keys] => hash [key] => [key_len] => [ref] => [rows] => 1 [Extra] => ) ) [1] => Array ( [0] => SELECT * FROM tl_user WHERE id='1' [1] => 1 rows returned [2] => Array ( [id] => 1 [select_type] => SIMPLE [table] => tl_user [type] => const [possible_keys] => PRIMARY [key] => PRIMARY [key_len] => 4 [ref] => const [rows] => 1 [Extra] => ) ) [2] => Array ( [0] => SELECT * FROM tl_user_group WHERE id=NULL AND disable!=1 AND (start='' OR start<1278927715) AND (stop='' OR stop>1278927715) LIMIT 0,1 [1] => 0 rows returned [2] => Array ( [id] => 1 [select_type] => SIMPLE [table] => [type] => [possible_keys] => [key] => [key_len] => [ref] => [rows] => [Extra] => Impossible WHERE noticed after reading const tables ) ) [3] => Array ( [0] => UPDATE tl_session SET tstamp=1278927715 WHERE sessionID='vabeo29tmr11ngumcojkgk38f4' [1] => 0 rows affected ) [4] => Array ( [0] => SELECT * FROM tl_playlist WHERE id='13' LIMIT 0,1 [1] => 1 rows returned [2] => Array ( [id] => 1 [select_type] => SIMPLE [table] => tl_playlist [type] => const [possible_keys] => PRIMARY [key] => PRIMARY [key_len] => 4 [ref] => const [rows] => 1 [Extra] => ) ) [5] => Array ( [0] => SELECT * FROM tl_playlistitems WHERE pid='13' ORDER BY sorting [1] => 11 rows returned [2] => Array ( [id] => 1 [select_type] => SIMPLE [table] => tl_playlistitems [type] => ref [possible_keys] => pid [key] => pid [key_len] => 4 [ref] => const [rows] => 21 [Extra] => Using where; Using filesort ) ) [6] => Array ( [0] => UPDATE tl_playlist SET playlistxmlexists = 1 WHERE id=13 [1] => 0 rows affected ) [7] => Array ( [0] => UPDATE tl_playlistsubject SET subjectxmlexists = 1 WHERE id=9 [1] => 0 rows affected ) [8] => Array ( [0] => DELETE FROM tl_playlistitems WHERE NOT EXISTS (SELECT * FROM tl_playlist WHERE tl_playlistitems.pid = tl_playlist.id) [1] => 0 rows affected ) [9] => Array ( [0] => SHOW COLUMNS FROM `tl_playlistitems` [1] => 19 rows affected ) [10] => Array ( [0] => SELECT DISTINCT(filetype) FROM tl_playlistitems WHERE pid='13' [1] => 3 rows returned [2] => Array ( [id] => 1 [select_type] => SIMPLE [table] => tl_playlistitems [type] => ref [possible_keys] => pid [key] => pid [key_len] => 4 [ref] => const [rows] => 21 [Extra] => Using where; Using temporary ) ) [11] => Array ( [0] => SELECT DISTINCT(pubdate) FROM tl_playlistitems WHERE pid='13' [1] => 5 rows returned [2] => Array ( [id] => 1 [select_type] => SIMPLE [table] => tl_playlistitems [type] => ref [possible_keys] => pid [key] => pid [key_len] => 4 [ref] => const [rows] => 21 [Extra] => Using where; Using temporary ) ) [12] => Array ( [0] => SELECT COUNT(*) AS total FROM tl_playlistitems WHERE pid='13' [1] => 1 rows returned [2] => Array ( [id] => 1 [select_type] => SIMPLE [table] => tl_playlistitems [type] => ref [possible_keys] => pid [key] => pid [key_len] => 4 [ref] => const [rows] => 21 [Extra] => Using index ) ) )

as opposed to BELOW... the debug info just listing the records (NOT using show all, using show records instead)... which has one extra array [13]to it. This lists all 11 records correctly.

Code:

Array ( [0] => Array ( [0] => SELECT * FROM tl_session WHERE hash='d14c5be9d8a482c376178a1e7a3d09ce4bb49fe2' AND name='BE_USER_AUTH' [1] => 1 rows returned [2] => Array ( [id] => 1 [select_type] => SIMPLE [table] => tl_session [type] => system [possible_keys] => hash [key] => [key_len] => [ref] => [rows] => 1 [Extra] => ) ) [1] => Array ( [0] => SELECT * FROM tl_user WHERE id='1' [1] => 1 rows returned [2] => Array ( [id] => 1 [select_type] => SIMPLE [table] => tl_user [type] => const [possible_keys] => PRIMARY [key] => PRIMARY [key_len] => 4 [ref] => const [rows] => 1 [Extra] => ) ) [2] => Array ( [0] => SELECT * FROM tl_user_group WHERE id=NULL AND disable!=1 AND (start='' OR start<1278927855) AND (stop='' OR stop>1278927855) LIMIT 0,1 [1] => 0 rows returned [2] => Array ( [id] => 1 [select_type] => SIMPLE [table] => [type] => [possible_keys] => [key] => [key_len] => [ref] => [rows] => [Extra] => Impossible WHERE noticed after reading const tables ) ) [3] => Array ( [0] => UPDATE tl_session SET tstamp=1278927855 WHERE sessionID='vabeo29tmr11ngumcojkgk38f4' [1] => 1 rows affected ) [4] => Array ( [0] => SELECT * FROM tl_playlist WHERE id='13' LIMIT 0,1 [1] => 1 rows returned [2] => Array ( [id] => 1 [select_type] => SIMPLE [table] => tl_playlist [type] => const [possible_keys] => PRIMARY [key] => PRIMARY [key_len] => 4 [ref] => const [rows] => 1 [Extra] => ) ) [5] => Array ( [0] => SELECT * FROM tl_playlistitems WHERE pid='13' ORDER BY sorting [1] => 11 rows returned [2] => Array ( [id] => 1 [select_type] => SIMPLE [table] => tl_playlistitems [type] => ref [possible_keys] => pid [key] => pid [key_len] => 4 [ref] => const [rows] => 21 [Extra] => Using where; Using filesort ) ) [6] => Array ( [0] => UPDATE tl_playlist SET playlistxmlexists = 1 WHERE id=13 [1] => 0 rows affected ) [7] => Array ( [0] => UPDATE tl_playlistsubject SET subjectxmlexists = 1 WHERE id=9 [1] => 0 rows affected ) [8] => Array ( [0] => DELETE FROM tl_playlistitems WHERE NOT EXISTS (SELECT * FROM tl_playlist WHERE tl_playlistitems.pid = tl_playlist.id) [1] => 0 rows affected ) [9] => Array ( [0] => SHOW COLUMNS FROM `tl_playlistitems` [1] => 19 rows affected ) [10] => Array ( [0] => SELECT DISTINCT(filetype) FROM tl_playlistitems WHERE pid='13' [1] => 3 rows returned [2] => Array ( [id] => 1 [select_type] => SIMPLE [table] => tl_playlistitems [type] => ref [possible_keys] => pid [key] => pid [key_len] => 4 [ref] => const [rows] => 21 [Extra] => Using where; Using temporary ) ) [11] => Array ( [0] => SELECT DISTINCT(pubdate) FROM tl_playlistitems WHERE pid='13' [1] => 5 rows returned [2] => Array ( [id] => 1 [select_type] => SIMPLE [table] => tl_playlistitems [type] => ref [possible_keys] => pid [key] => pid [key_len] => 4 [ref] => const [rows] => 21 [Extra] => Using where; Using temporary ) ) [12] => Array ( [0] => SELECT COUNT(*) AS total FROM tl_playlistitems WHERE pid='13' [1] => 1 rows returned [2] => Array ( [id] => 1 [select_type] => SIMPLE [table] => tl_playlistitems [type] => ref [possible_keys] => pid [key] => pid [key_len] => 4 [ref] => const [rows] => 21 [Extra] => Using index ) ) [13] => Array ( [0] => SELECT * FROM tl_playlistitems WHERE pid='13' ORDER BY sorting LIMIT 0,30 [1] => 11 rows returned [2] => Array ( [id] => 1 [select_type] => SIMPLE [table] => tl_playlistitems [type] => ref [possible_keys] => pid [key] => pid [key_len] => 4 [ref] => const [rows] => 21 [Extra] => Using where; Using filesort ) ) )

Maybe someone can tell from that whats going on.

Two asides:

Thyon - my 1:4:4 back buttons all work when I use Contao 2.9... a two year problem solved!! I'm so happy.
Leo Thanks heaps!

Re: Ghost entries

This number of arrays thing must have something to do with it,....

When both "show records" and "show all" render correctly the number of arrays are identical.
When the "show all" renders incorrectly there is one less array than with the "show records".

Also there is a pattern to it.
My 11 record ids are correctly rendered as 500,25,24,21,26,19,27,20,23,18,22 (they're being rendered alphabetically).
"Show all" renders them as blank(no id), 500, blank,25,blank,24,blank,21,blank,26,blank.
So the first half are rendered correctly, but interspersed with the second half which are not.

Its a bit elaborate, but does yours do exactly the same Sares??

Re: Ghost entries

Hi Ramjet,

Quote:

Originally Posted by ramjet

Its a bit elaborate, but does yours do exactly the same Sares??

yes, I have the same situation here, it's always blank, id, blank, id etc.

Kind regards,
Sares

Re: Ghost entries

OK....
I've corrected this in my module. It seems to be a problem with 'list'=>'Sorting'=>'fields'=> array('sorting') when only 'sorting' is used.
I can't figure this though, as for instance in tl_faq.php Leo just uses array('sorting').

My DCA with the problem:

Code:

'list' => array ( 'sorting' => array ( 'mode' => 4, 'fields' => array('sorting'), 'flag' => 1, 'panelLayout' => 'filter;search,limit', 'headerFields' => array('listtitle','listdescription','playlisttype','addplaylistimage'), 'child_record_callback' => array('tl_playlistitems', 'renderPlaylistItems') ),

and corrected by adding in another field ('title') to sort by:

Code:

'list' => array ( 'sorting' => array ( 'mode' => 4, 'fields' => array('sorting','title'), 'flag' => 1, 'panelLayout' => 'filter;search,limit', 'headerFields' => array('listtitle','listdescription','playlisttype','addplaylistimage'), 'child_record_callback' => array('tl_playlistitems', 'renderPlaylistItems') ),

This seems to correct the problem and still allows draggable sorting in the child records.
I know this isn't the proper solution, but it does correct this problem.

I notice in your tl_catalog_fields Thyon you have the same

Code:

'fields' => array('sorting')

so probably

Code:

'fields' => array('sorting','name')

will fix this.

You might want to try this out Sares, by altering system/modules/catalog/dca/tl_catalog_fields as above, to see if it fixes it.
As to why, I have no idea.

Re: Ghost entries

Hi Ramjet,

Quote:

Originally Posted by ramjet

You might want to try this out Sares, by altering system/modules/catalog/dca/tl_catalog_fields as above, to see if it fixes it.

thank you very much for your deep investigations and your help!
I've added your fix and it seems to work fine. Now all ghost entries disappeared.

Maybe Thyon has an idea, what the problem might be, but for now I am happy with
this solution.

Many thanks!

Kind regards,
Sares

Re: Ghost entries

Good to know this fixed it for you too.
But its a mystery to me, i've tried altering/omitting the flags, omitting the label section, adding sorting/flag=>2 as a field and generally trying to make sure there is no difference in structure to tl_faq, all to no avail.
I know we should be able to just use 'sorting' on its own, but i just can't find the reason "show all" omits the last array that "show records" processes.
Perhaps its something to do with the parent table?
Maybe Leo might see something obvious going on.

Re: Ghost entries

This is because the catalog doesn't yet implement the new eval 'ignoreSorting' variable. Leo has changed it so that he automatically detects the sorting value in the listing display. Just change the tl_catalog_items pernanently, because that section is actually dynamically overwritten with a callback to display the items.

Re: Ghost entries

Hi Thyon,

I don't exactly understand everything you wrote, so just a simple question:
Is ramjets fix safe for 2.8.x without any side-effects and is it the recommended
way to do so?

Many thanks and kind regards,
Sares

Re: Ghost entries

Quote:

Originally Posted by thyon

This is because the catalog doesn't yet implement the new eval 'ignoreSorting' variable. Leo has changed it so that he automatically detects the sorting value in the listing display. Just change the tl_catalog_items pernanently, because that section is actually dynamically overwritten with a callback to display the items.

Hi Thyon
I have the same problem in a catalog.
What should I do to correct the list of fields?

Re: Ghost entries

Quote:

Originally Posted by PaoloB

Hi Thyon
I have the same problem in a catalog.
What should I do to correct the list of fields?

:) ok, i have read all the topic and found the solution, thanks