Autopilot · Robot · 3 posts

Autopilot · Robot · 3 posts

This is on the topic where the reply hangs the editor even though it does post the reply.  There is no link to the second page that Autopilot is suppose to create.

I am poking around in the database and I see where it appears to have created the link.  Anyone knows how this autopilot thing is suppose to work?  What should I look for in the database?

The division is there but no link.  Furthermore, when I try to navigate to the second part manually; entering the URL into my browser, I get a not found error.

OK, I see how this works, Autopilot creates a post in the first part with a link that points to a new topic with the same name + "- part 2"; I wonder how SMF handles this?  It started the process but since the posting hangs on this "bug" I have, it could not finished it; it did not create the new topic for part 2.  Therefore, I can manually enter the second part of the topic in the database.  Or, if I can fix the bug, I could delete the first attempt and let autopilot (that needs to be changed) do its thing again.

I don't like the autopilot solution for multi-page topics so I am going to kill it.  Most topics won't run that long but if they do they just do.  Autopilot breaks the topic; it kills the topic, and creates a new one.  That solution is not very elegant.  How does the stand-alone forums handle this?

How about a page solution?  Each reply is stored in its own row in the database.  I actually prefer a last entry first listing; with multiple pages it makes it easier to read the forum without having to dig back through the pages of the topic.  You pull out the last XX number of replies and display them with pagination to the earlier replies.  When you click on the next page it pulls out the next XX number of replies and so forth.

Just been over at Andrew's blog on this autopilot thing; and even though it was last year decided to throw my opinions in.  I can not help but think this solution was implemented not because it was a good solution but an easy solution.  Posts exceed 50, make a new topic and lock the old one. Easy peasy but a bad idea.  Oh, and there is no config file as Andrew said, it is part of the header.  One should be able to set in the backend the number of posts before the topic is locked and a new one created.  From what Andrew said, it does not matter what the users of Dolphin think about autopilot, you are going to have it even if you don't want it; much like your Mum putting spinach on your plate.

http://www.boonex.com/trac/dolphin/ticket/3040