 | | |
|
dougthompson
User
Oct 25, 2006, 8:59 AM
Post #1 of 4
(404 views)
Shortcut
|
A few things I've noticed as we continue to deploy AM 2.0
1--Creating a separate article index to hold a specific category and then excluding that category from the global index isn't working properly on our installation. For example, we created a "news" category and assigned it am index publishing rule separate from the global index. We set it to "include" only the "news" category and then "excluded" the "news" category from the globalindex rule. On first publish, everything worked as planned. We placed a placeholder for the "news" index at the top of the page and added a story.
However, when we added a story to the globalindex it published the "news" category story in both indexes. Then a new story was added to the global index and it showed up in both indexes even though it was not the "news" category indicated in the new index. (The "news" index was set to list just one story and the "globalindex" was set to list 20 stories.
We devised a workaround by adding a "rank" field and then setting the "news index" to publish the latest story ranked "1" and set the global index to start its listing with the second highest story on the list.
Are we missing something?
2--Went back and added a story that, somehow, got dropped from the conversion. Set the date for September when the story was published but it showed up as one of the top 10 stories in the global index. Only way to resolve the problem was to hide the story until it cycled off the top 20 story listing. Saw something similar posted by someone here who edited an old story and it moved up in rankings even though the publish date had not changed.
Any ideas?
Doug
|
|
| |
|
Dave
Staff
/ Moderator
Oct 25, 2006, 9:30 AM
Post #2 of 4
(396 views)
Shortcut
|
|
Re: [dougthompson] Apparent bugs
[In reply to]
|
Can't Post
|
|
Hi Doug,
Thanks for the report. The easiest way for me to investigate the publish rule issue would be if you could send me a artman2 link and login info for your server (via forum private message or email).
If anything is mis-configured I can let you know what that is, or if there is a bug with that feature then I'll get it fixed ASAP and send you a patch.
Regarding the sorting problem. Are you using MySQL and a "featured" field? Try changing your featured field from a "memo" to an "int" in the database editor. The "int" field is numeric and MySQL seemed to have some sorting issues with the "memo" on an install I saw the other day.
Hope that helps. We're here to help you make it work, let us know if you have any other difficulties!
Dave Edis - Senior Developer
interactivetools.com
|
|
| |
|
dougthompson
User
Oct 26, 2006, 8:45 AM
Post #3 of 4
(357 views)
Shortcut
|
Dave:
Thanks for the response. I'm not sure you can tell from the settings I have not because I changed them around to create a situation that works. When I get a chance, I'll try to recreate the rules that I had before that did not work.
Doug
|
|
| |
|
Strani
User
Oct 27, 2006, 8:02 AM
Post #4 of 4
(334 views)
Shortcut
|
|
Re: [dougthompson] Apparent bugs
[In reply to]
|
Can't Post
|
|
A response to the order problem: It was suggested that MySQL might have to do with it but I used the featured field to 'int' solution to solve my problem, while I don't use MySQL yet.
So, changing artfield_20 (featured) from memo to int does help, but I doubt that it's caused by MySQL.
Jonathan
|
|
| |
|
