Tiki Tiki

well i have decided to go ahead and purchase a license for ipb for my current vb fourms at the end of october

I have, multiple times. How many times do I have to say it? Look at the competition, look at their documentation, that is a perfect example of a well written, proper documentation manual, and it's not hard to keep up to date. It's a win/win situation.




I'm not going to continue to log helpdesk request after helpdesk request with garbage such as "how do I do this". That wastes MY time and your time.
Inline help does not do that, yet, and it shouldn't ever.
A "quick start guide" doesn't do that now and shouldn't ever do that
Articles are entirely too wordy for that, and entirely too opinion based.
A flat out manual, properly indexed, properly updated would resolve this.

Since IPB doesn't want to do this (will not) , there's really no further need for discussion. I'm sorry that you can't see the need for it, but that's your problem not mine.
When it comes down to it, the excuses from IPS and IPB have turned me away from the product itself. As I stated in my blog, I'm thankful it was only a $20 investment, because it certainly was a loss, but I'm not going to continue to waste my time trying to figure out where things are at, or how to do this, all because someone doesn't want to write proper documentation.

While I sympathize with your position, this line really doesn't work.
Sure, documentation doesn't "write itself", but then again, neither does code. As this stuff is written, it should be documented, not as an afterthought.



so, which is it? Will there be a manual, or will there not be a manual? Please, do clarify.

The types of documentation described previously work somewhat well (though articles are not documentation by any means) for new users, yet these do not relieve the need for a manual of some kind.

Getting started guides, great idea, and could easily be a 'chapter' in the manual, but definitely don't take the place of it.
Inline help, as well, great idea, but this doesn't cover everything at all, and it shouldn't.
Articles, too wordy and opinion based, definitely not documentation.

There needs to be some sort of manual here, which, as already said before (not by me, mind you) would cut down on needs for support , and promote some sort of customer satisfaction. Somewhere a customer can go and say "ahah, THIS is how I do this", whether it's an advanced customer wanting to learn how to change a theme, or a new customer just wanting a step by step guide to creating a new forum. Both of those are just examples, but you still have a major need for documentation here , because the product obviously does not document itself.

I have commented on this before. It would be nice if IP.Board had provisions for both a "Terms of Use" page and a "Privacy Policy" page

I have commented on this before. It would be nice if IP.Board had provisions for both a "Terms of Use" page and a "Privacy Policy" page

IPS Staff: I hate to say this but the IPS Upgrades are becoming a real inconvenient Annoyance.

What am I talking about? Everytime there is a service update to IPB (2.0.1, 3.0.2, etc) the upgrade creates havok with the hooks that I have installed. Not only do I have to disable the hooks, but, they have to be un-installed and then re-installed. The upgrades are not anticipating already installed hooks and adjusting for them and it's becoming an annoyance.

Does IPS plan on fixing this problem or is this going to be a regular 'romp and stomp' action with every upgrade/update? For one, I would love to see this corrected.

Is it possible to call the folder board_3_0_3 say rather than just board.

Reason being is that when it is extracted onto the computer it saves a) overwriting the previous version and/or b) having to manually create a folder for it.

Thanks.

In IP.Board 2.x, on the page where we manage our skin templates, you could easily tell which skin group had one or more modified skin templates in it as the little icon beside it would be red. This functionality was removed in 3.x. I found this to be helpful for a number of reasons, and would like to see it return.

First, if an upgrade to the forum software modifies some skin templates, the upgrade script won't touch your modified skin template groups, and you'll have to patch those manually. When we look at a difference report, we used to be able to quickly see whether or not any of the templates changed in this new version needed this manual patching; if you could see that only 3 of your skin's template groups had been modified it made the job of patching a whole lot quicker. Secondly, it can be kind of an annoyance on a development board where you do things like test out code snippets. Again, when you upgrade that board, any modified templates you had won't get updated, so you may run into issues where you just fiddled with a bit of code, forgot to revert it, and now you have some code for the page that is out of whack.

Under "Manage Applications & Modules" I think it should be possible to order the links regardless of their category. Please consider adding the ability to reorder like this for a future release. My desired order would be:

CCS | Forums | Blog | Gallery | Members | Calendar | Subscriptions


Kindest Regards,

Andrew

I'd like to see the LoFi skin work better on the iPhone or maybe a new skin derived from the LoFi skin for iPhone use.

The main problem, at least when using Safari on my iPhone, is that the fonts are so small and the page so wide that I have to keep zooming in on each page to see the text and choose links.

I haven't researched it, but there must be some way to make this work.

When I browse to m.google.com with my browser user agent set to pretend to be an iPhone, I see that the page is formatted specifically for the iPhone so that the page fits the phone's screen exactly and the fonts are large enough to be seen.

Just a quick look at the source for the page as seen by an iPhone, shows:



meta name="viewport" content="width=device-width,initial-scale=1.0,maximum-scale=1.0,user-scalable=0"

There is some other header html that might be making this work better.

Anyway, that is my suggestion... make Lo Fi work better on the iPhone.

Currently if you go to someone's profile and try to send them a PM, if you decide you need all the editor options you don't have them, and there isn't a way to get to them short of copying what you typed so far, going to your messenger, typing in the name of the member, and pasting what you had written...

There really needs to be a link on the "Quick PM" popup like their is on the fast reply, "Use Full Editor" which keeps what you'd written, who you're sending it to, and takes you to your messenger to send a PM with access to all the editor options.

We will be providing more information on this soon. Our priorities have been with IPB and getting it fixed up and stable for as many customers as possible first. :)

[Originally posted in the Tracker as Report ID #17058: Portal Page Title]

I'm sure this is "normal behavior," and not a "bug," but it doesn't work very well...

Portal set as default app and being used as one-and-only home page for the website...

You have to include the name of your website in the 'IPB Portal Page Title' box or you end up with a very non-descriptive title for your website's landing page. The inclination is to name the portal "Portal," but now your website's landing page is simply "Portal." Not good.

The problem is that when you add the name of your website to the title (e.g., "MyAmazingSite Portal"), you now get a breadcrumb trail that looks like this:

MyAmazingSite > MyAmazingSite Portal

or

MyAmazingSite Forums > MyAmazingSite Portal

Redundant, to say the least, since you really want something like this:

MyAmazingSite > Portal

Again, not necessarily a "bug," but shouldn't there be more control over the Portal's page title when it's a given that some websites are going to be using it as the default app / landing page?

And four days would be .57 weeks. :D

And four days would be .57 weeks. :D