- You can very well hide any of the fields from your users.
- Concerning accessing the database from your own scripts we cannot and will not comment on, as it is against copyright laws. Whether you can find a way to do this on your own is your own choice.
Huh? How does copyright apply at all? First, who owns the copyright? Second, if the data is just sitting in a database, that's all they have to say. That's not a copyright violation. Third, who would release a product like this and then be upset if I cribbed a few lines of code to make the product actually useful on the site it's legally licensed for?
She gave some feedback on the site, and threw together a mock-up. I sent it on to dad, with my comments.
Darn. So close.
I think the box model is missing one piece.
It's too bad this likely-kinda-common situation wasn't addressed, somehow. I can see those borders causing constant headaches. The problem is, it's one of those 50-50 situations. Sometimes you'd want to specify the outer extents of the box, including border and margins. Other times, you'd want to specify the internal dimensions of the box, and the margin and borders just fall where they may.
If it were me, I would have provided a method to tell the renderer what to include within the box extents. I can see situations where I would want to define the edge of the box to include the padding, the border, or the margins.
Also, the password file has to be maintained by hand. I guess I could write a PHP script to do that
Trying to figure out what to work on next. Should I look for content to pour in?
I think my dad wants me to start looking at getting the database integrated. I guess I need to ask him which is more important: Starting to learn the database stuff, or finishing a "Here we are" launch.
Idea: Store links in database, so anyone can change it?
Idea: Store all content in database, so that the primary version is on the website?
Nah, don't like either of those.
Idea: Need maintenance page(s) that's not linked to from any of these pages. Things like a link to edit the Company News blog, Calendar of events, etc.
Idea: Build the MM2 submenus dynamically from a database. That would double as the source of the sitemap
Spent a few mins looking for automated sitemap generators. It's difficult to come up with a search phrase that doesn't pull up nearly every actual sitemap.
Out: 02:15
Couldn't figure out how to view my first entry. Turns out, there's a documentation confusion. There's a "Public HTML" field, which apparently is used to report changes to your blog to some central places. And there's a field that mentions the MT index. Well, I thought that index had something to do with the database. Turns out, they mean the index.html file.
Now I've got that off my mind and I can actually get to work. Next for this will be looking at how to customize it and organize it and fit it into the rest of my site.