As for the blocks can't you just include the check yourself? It is what I do, I built a login block for a home page, if the member was logged in, it would show a welcome block, if they were not, then it would show the login box.
Yeah will be a wiki system so that members can add and edit players, each player will have a team set, and its that field then that the template will grab depending on the team being viewed. I had it working on my current site, but stopped it as was redesigning how it will all work.
This was what i got at the time i stopped to restart how it would all look. (ignore the image, hadn't re-sized it, and ignore Messi lol) that was just to test it setting the layout based on the players positions.
The team info, and stadium info will also be a wiki database. But league tables and so on will not, as that's based off an external feed.
Not exactly a content page as such, but been working on something for a new design of my site.
I am using IPC Databases to create the latest news, tables sections, along with a database that allows me to set the teams banner image. Works in both forum and topic view. And is based off the forum name and then grabs the relevant teams banner.
Still a work in progress and am redesigning it to work with a team home page that will link to forums and other area's for that team.
That is just a mockup at the moment, but will be sorting it all out over the next few days once I figure out what bits and bobs I want on a teams home page.
All but the forums will then be run via content databases.
Took me a while to find it at first too, but after using it, I much prefer it to the old ugly looking icon alongside the topic title, its clean and easy when you get used to it, its just knowing it is there can take a while ;)
But isn't there a way to release a list of cookies that the IPS suite use, and allow those who want to add the relevant sections to their site, to do so. It doesn't then affect those who don't need it, but greatly helps those who are looking for that information.
The licence system is changing, yes, but not in the way you are explaining.
Basically at the moment you require IP.Board to use the otehr products like Nexus.
What IPS are doing, is making the main product IP.Community (or whatever it will be called) then IP.Board will act like the other current extra's. In that those who want Nexus, but not IP.Board, won't need to puurchase IP.Board.
Currently its like this
- And so on....
It will become
IP.Community (again cant recall the actual name)
- and so on.
So you would still be required to purchase them individually, it just allows a site to be created without the requirement of IP.Board
As for your question about that site, yes you can do all that in IP.Content, it is a great bit of kit, although I am only now really gettting stuck in with trying things out on it. But you can create your custom feed blocks and so from it.
If I am not mistaken, you can set Content as your primary add-on, and leave the forum inside the root at the same time. All you have to do is add a line into constants.php to set Content as your landing page.
What if you have hundreds upon hundreds of forums, that all members are to have access too. That forum index doesnt half get a bit long. And the amount of clicking and scrolling can be a pain. I wanted to create a forum for 1 section, a forum for another to make it easier, but currently it means different sites, linked by converge, which wouldn't be ay good as, if member a wants to contact member b, that PM is prob not going to be on the same site. So one back end would allow for that sort of setup.
I could have a separate forum for football, a separate for rugby and so on. All linked so members can use them all without any efforts on their behalf.