You are not logged in. Please login or register.


Post new reply

ochiba forum → Discuss → Other feature suggestions → Post new reply

Post new reply

Compose and post your new reply

You may use: BBCode

All fields with bold label must be completed before the form is submitted.

Required information for guests


Required information

(delete this if you are not)

Topic review (newest first)

19

If they weren't lame and coded for MySQL only, I might've recommended Vanilla :|

18

I actually used to use PunBB on my site before, but I want something a bit less formal.

I'm really fascinated by the nature of discussion that takes place on sites like 2ch because of the anonimity of the system.

17

You sure you wouldn't rather run something more feature-full as a discussion board? PunBB is pretty nice.

In any case, what you described should be doable strictly via stylesheets, so I'll play around with it...

16

Cool, would be nice if the configs and stylesheets to run a discussion only board were included in the next release (hint hint)... :P

15

kaa wrote:

Not sure if this is appropriate for this script. But is it possible to run the script as just a message board? (basically, a PHP version of Kareha).

Feature-wise, yup, it could. Out of the box, even.

However, the layout is really geared towards the display of images, so if you wanted a discussion-only solution, then you might want to tweak images.tmpl to make it more text-friendly, and maybe remove the file inputs on the post forms.

14

Not sure if this is appropriate for this script. But is it possible to run the script as just a message board? (basically, a PHP version of Kareha).

Lol, that's actually a feature removal request come to think of it.

13

Odd. Where did you add the lines? They should go in display(), like right after line 159 (which should be the FOOTER line).

12

{NEWS}

Fatal error: Call to a member function setVariable() on a non-object in /home/ken/public_html/log/includes/page.php on line 132

doh

11

just trying to include some navigation which i have across my site, and maybe a news.php for the home section.

Aah.

A couple of ways to go about it, depending on how complex things are, fiddle with site.tmpl and includes/page.php and try to incorporate those into ochiba.

For example, put "{NEWS}" into site.tmpl somewhere. Then in page.php, in the display() function, add something like:

ob_start();
include("news.php");
$news = ob_get_contents();
ob_get_clean();
$tmpl->setVariable("NEWS",$news);

Not very efficient, but it should do the trick.

10

just trying to include some navigation which i have across my site, and maybe a news.php for the home section.

9

siik wrote:

no, not an options section for the admin to change, but for any user visiting to change.

Oh, I see. Yeah, I had started on something like this originally because I really wanted users to be able to specify their time zone.

However, any user-customized output makes the caching system invalid, so I abandoned the idea. I dunno, I guess these can be features you can enable if you want to give up the caching.

As for css selection, you can add your own to the menu (templates/site.tmpl) and use something like the following for each stylesheet offered:

<a href="javascript:void null" onclick="setActiveStyleSheet('ochiba'); return false;">ochiba</a>

It'll cookie and save the selection.

also just ran into some php problems with your templates, as in it won't parse. i leave an <? include "this" ?> and it stays that way in the output. should i be editing something else, like index itself? i don't want to 'break' anything.

Aah, the template files are not PHP files, so code won't work. If you could give me more details about what you're trying to do, I can make a suggestion (which template, which page, what you are including, etc).

8

web-based interface to conf.php

no, not an options section for the admin to change, but for any user visiting to change. sort of like that css bar on top of wakaba, the cookie saves the option right? maybe the posts per page and truncate thing are too much, but i'd like to have a css selectable section, without using view > page styles.

also just ran into some php problems with your templates, as in it won't parse. i leave an <? include "this" ?> and it stays that way in the output. should i be editing something else, like index itself? i don't want to 'break' anything.

7

siik wrote:

also chiming in about category-centric feature-restrict. maybe even category-centric bbs mode and image reply mode (no image posts in one cat)

It should be doable by installing ochiba twice, one in open-posting mode, one in restricted mode. Give them the same look, share a menu, and it should be mostly transparent as far as visitors go.

an options section where someone/anyone can define their own posts per page, truncated posts per thread, css

You mean a web-based interface to conf.php? Something to consider, I suppose, but conf.php is meant to be edit once, and not think about it anymore, so I haven't felt it was a good place to spend time on an interface you'll use very infrequently.

a popular keywords section ala flickr

Interesting idea... I'll have to play around with this.

default category, instead of /home

mod_rewrite is your friend!

maybe pinging of blog servers for photolog/moblog purposes? maybe even some rss enclosure stuff so it can podcast too?

Interesting, interesting... I haven't really delved into the RSS side of things other than just getting it up, but it is an area I would like to expand.

later on i will volunteer to make a languages.txt so you can just include it and have all the text and stuff from that

That would be great. I've gotten a little sloppy with things, but the strings.php is an easy place to start, I hope.

lemme know how you do on the iframe/divs instead of popups

I actually got it to render OK in IE. See http://ochiba.x-maru.org/test/ for a sample of a new idea for the posting and searching interfaces. It's not a full ochiba install, just a few sample pages to illustrate where I'm going. Rather than a opening a whole new window, the post and search boxes will appear via dynamically generated content, via DOM stuff (kind of like the "Another File" option for posting).

Another idea I had is to use XmlHttpRequest to "pre-validate" verification codes, so that the POST doesn't officially begin until the verification code has checked out. This will save an a lot of headache, I think (be quicker, too).

6

so now that i've had a chance to see the source and mess with it, here are some feature requests, and maybe requests that are already implemented and idunno how to get to it:

-also chiming in about category-centric feature-restrict. maybe even category-centric bbs mode and image reply mode (no image posts in one cat)
-an options section where someone/anyone can define their own posts per page, truncated posts per thread, css
-a popular keywords section ala flickr ( http://flickr.com/photos/tags/ )
-default category, instead of /home
-actual 'album' and 'imgboard' modes, since i think albums should look a little different than the imgboard theme. i'll show you mockups of what i mean.
-maybe pinging of blog servers for photolog/moblog purposes? maybe even some rss enclosure stuff so it can podcast too?


later on i will volunteer to make a languages.txt so you can just include it and have all the text and stuff from that. easier to aesthetically customize and surely later on someone will want translations.

lemme know how you do on the iframe/divs instead of popups. while i love the script to death, the popups still get me.

5

7hs wrote:

Another bug (although it might be in imagemagick or PHP): ochiba seems not to understand very large animated gifs such as http://muchan.org/stuff/msca-001-afk-gogo.gif . It says "unrecognized file type."

That file comes up as about 4.4MB, which is greater than then the 2,000,000 bytes defined as the maximum file size accepted by ochiba (see MAXIMUM_SIZE in conf.php). The thing is, even if you adjust this value greater, PHP itself will reject uploads up to a certain size, as defined in php.ini, and unless you have administrative control, there's not much you can do, other than ask your hoster to increase it. The relevant paramters in php.ini are post_max_size and upload_max_filesize. Apache itself also has possible limits, but generally, those don't come into play.

I'm pretty sure that's what you are running into.

ochiba forum → Discuss → Other feature suggestions → Post new reply



Generated in 0.034 seconds (64% PHP - 36% DB) with 9 queries