Good spot. Disabling the mod had no effect (I'd already tried that before coming for help), but within the Advanced Tags and Prefixes mod there's a "Fix Database" button. It claimed to nothing but in fact resolved my problem.
My board is throwing PHP warnings on the main page:
I've recached all skins, which is the usual advice, to no avail.
I've just dropped out of support and messed something up with the invoice - its now disappeared. While I get Sales to generate a new one, can anyone suggest a fix? Its a bit of an issue as it exposes things we shouldn't expose.
This is a question to which I think the answer could be easy, if functionality exists. I have heavily customised IP.Content on my site, and I'm using custom tables on my database, so I'm not always on the IPB reservation and am happy for custom work.
Okay, so I have a page on which I wish to display an image, amongst other things. The user should be able to select one of their images from IP.Gallery (not an album, it must be an image). I must get the ID of whatever image they picked so that I can store it to my database.
Is there a way to do this? To cause the 'My Media' pop-up to appear and restrict it to only images? Does this return a unique identifier?
we use IP.Content to allow certain users to auto-generate topics (12 users generate a total of 72 fixture-topics every wednesday). We have functionality that handles the titles and content (using the addTopic method in classPost), however we've just upgraded from 3.1.4 and have started using tags - actually, we're using the advanced tags & prefixes mod.
On week 1, for example, every topic starts with the text "MD1 - ", for Match Day 1. Next week its "MD2 - ", and so on. We have these set up as prefixes ("MD1", "MD2"), so currently moderators who post their threads manually can use the prefix whereas those who use the automated feature cannot use prefixes.
Is there a modification to addTopic() that allows for tags? Well, I'm sure there is, but can someone show me an example please? Specifically its prefixes we need now, but tags would be used fully if you have an example of that also.
I have defined the 100 tags for use in all forums, and I have defined those 11 prefixes for all forums also.
I understand there are limitations presently, so can you outline the best solution currently available to me?
Can I have a closed system of 111 'items' which can be used as either tags or prefixes, whichever the user wants?
(and if you're looking for feedback, please make tag selection use autocomplete rather than the drop down - after 10 items or so it becomes bad UI - though I understand this may be IPB rather than you)
I installed the mod and created a bunch of custom tags, closed system, everything looked fine. I then created my first prefix, I created only 11 of them. Not, when creating a topic, I can use any of the 11 new prefixed, but none of the (maybe 100) previous tags are available.
Do I have a setting wrong somewhere? I can't imagine tags and prefixes to be mutually exclusive (as I've read to the contrary).
$this->DB->build(array('select' => 't.ID, t.season, MAX( t.matchID ) AS TEST1, t.*',
'from' => array('bb_teams' => 't'),
'add_join' => array( 0 => array(
'select' => 's.matchID AS TEST2, s.*',
'from' => array('bb_matches_season' => 's'),
'where' => 't.matchID=s.matchID AND t.ID=s.teamID AND t.season=s.season AND s.isOpponentRecord=0 AND (s.matchesPlayed IS NOT NULL)'),
1 => array(
'select' => 'r.*',
'from' => array('bb_ref_races' => 'r'),
'where' => "t.idRaces=r.raceID"),
2 => array(
'select' => 'd.*',
'from' => array('bb_divs' => 'd'),
'where' => "t.division=d.divID")
'group' => 't.ID, t.season',
'where' => "$seasonQuery $divQuery $raceQuery $TVquery $CashQuery",
This is close to what I want. Without the joins I get the maximum t.matchID for each distinct group of (t.ID and t.season). However something is wrong with the join as TEST1 does not come out equal to TEST2 and the query takes absolutely ages.
Is there a way to join the tables on the MAX(t.matchID) and execute reasonably quickly or would it be better to have a reference table where I store the maximum matchID for a distinct group of (t.ID and t.season). To me that seems like annoying to maintain extra data but if it means much faster queries then I'll go with that solution.