Hi Alex, everyone,
I posted about this issue a few days ago but, i've done a little more digging and am wondering if the following might be able to shed any light on the problems that we've been having.
Here's my original post:
--
I'm having some problems getting the priority links modification (as seen in the modification forum of the Links Resources bit on this site which can be found at http://run-down.com/mods/links_sql_priority.php) to work with Links SQL 2.1
I had it working like a dream with Links SQL 2.05 but, since upgrading to the newer version if I set the build_sort_order_search variable under setup/search options to Is_premium as the field to sort against, it isn't playing ball. I have that column in the Links_Links table set up exactly as stipulated in the mod. (where the column is called Priority)
The strange thing is that I have set the variable build_sort_order_category to build using the same field and that seems to work absolutely fine..
I've tried reindexing the database, repairing the search etc. and none of that seems to help at all
Hope someone has an idea of what has changed in Links SQL 2.1 to cause this mod to stop working.
--
For a test we have selected a search based on the word "Royal" as we know that there are several links containing the word "royal" and 1 of them is a premium link. We have tried running the SQL command: select * from Links_Links where title like '%royal%' order by Is_premium DESC limit 5; which returns the values in the correct order. However, when using the Links search facility (with 'royal' as the search term) the premium link is at the bottom of the list instead of at the top (we use Is_premium to determine whether the link appears in the top part of the returned link list. If a link is a premium link the value is 1, 0 otherwise). The SQL command: select * from Links_Links where title like '%royal%' limit 3; returns the links in the same order as
they appear on the web page when using the search utility. We know that DBI is being used and we suspect that it may be to do with the way the results of the select statement are retrieved from the hash (since the 'order' is
incorrect). The Is_premium flag method worked fine under 2.05.
Hope somebody might be able to shed some light on the problem!
Cheers,
Hannah
I posted about this issue a few days ago but, i've done a little more digging and am wondering if the following might be able to shed any light on the problems that we've been having.
Here's my original post:
--
I'm having some problems getting the priority links modification (as seen in the modification forum of the Links Resources bit on this site which can be found at http://run-down.com/mods/links_sql_priority.php) to work with Links SQL 2.1
I had it working like a dream with Links SQL 2.05 but, since upgrading to the newer version if I set the build_sort_order_search variable under setup/search options to Is_premium as the field to sort against, it isn't playing ball. I have that column in the Links_Links table set up exactly as stipulated in the mod. (where the column is called Priority)
The strange thing is that I have set the variable build_sort_order_category to build using the same field and that seems to work absolutely fine..
I've tried reindexing the database, repairing the search etc. and none of that seems to help at all
Hope someone has an idea of what has changed in Links SQL 2.1 to cause this mod to stop working.
--
For a test we have selected a search based on the word "Royal" as we know that there are several links containing the word "royal" and 1 of them is a premium link. We have tried running the SQL command: select * from Links_Links where title like '%royal%' order by Is_premium DESC limit 5; which returns the values in the correct order. However, when using the Links search facility (with 'royal' as the search term) the premium link is at the bottom of the list instead of at the top (we use Is_premium to determine whether the link appears in the top part of the returned link list. If a link is a premium link the value is 1, 0 otherwise). The SQL command: select * from Links_Links where title like '%royal%' limit 3; returns the links in the same order as
they appear on the web page when using the search utility. We know that DBI is being used and we suspect that it may be to do with the way the results of the select statement are retrieved from the hash (since the 'order' is
incorrect). The Is_premium flag method worked fine under 2.05.
Hope somebody might be able to shed some light on the problem!
Cheers,
Hannah
search results sort order