[ Closed ] [Extension release] Last post subject on index (Page 1 of 3)

The directory name has to be: subject_index and not recent_index.

(isset($idmComp)) is redundant because the if/else statement ensures the definition of $idmComp.

Cheers smartys.

With these extensions there is still large room for confliction. Dont you think?

Erm... Nah.

I meant as in the above extension adds a left join for the topics as t. So now if someone creates another extension and trys the same thing there will be a problem?

That kind of confliction. It might not happen on this query but what about other queries.

I will test it this evening and come back to you. No reason why it should slow it down that much (that I can see).

I have quickly tested it on PunDemo and the time does not change by much.

0.022 without
0.058 with

EDIT:
Ok the more forums you have the more strain.

You mean if another extension tries to add a left join? Yes, I suppose, but I think you might be overestimating how often an extension would want to do similar things (assuming of course there is no conflicting functionality). It's something to consider though: we might force extension writers to use topics AS <t_<ext_id>, for example.

Added an index on last_post_id in the topics table which fixed the delay.

Will release a new version tommorow.

@Bingiman: Will do...
@qubertman: Yep that fixes it. Im including it next release.
@orlandu63: Trying to think of a way around this... Will look at replacing first two items in array instead of clearing array.

Please add the date/time information of the post.

Will do and will do...

For titles less than 30 characters, the title attribute is being assigned the previous title greater than 30.