Hi,
I just installed Ochiba, and according to the manual I should now go to the /admin part and set up a tripcode. However, I get a 404 when I try to visit this location. The installation directory doesn't show either a directory or php script called admin.
Am I doing something wrong here ?
Hmm, that sounds like your system doesn't have mod_rewrite available. What happens if you go to /index.php/admin? Does it show up then?
If that is the case, then I would recommend bugging your hoster to enable mod_rewrite for your directory - ochiba uses it a lot (which is why you don't actually see any files at the top level, other than index.php).
The other alternative is to live with "ugly" URLs such as the one above. Offhand, I know you would have to change the define() for ROOT in conf.php to include the "index.php/" part but I can't say if this would be sufficient.
you know, like 5 or 6 other 'browse' inputs for uploading. what do you think?
>i get what you mean, a toggle and somethign with on.focus or some other java.
Yah, something like that. On the current posting form, there would be a button labelled "Add another file", and when the user clicked it, another file input and comment textarea would appear via Javascript.
>i just don't like popups because opening new browser instances
Somewhat understandable. I really despise having the form just sitting there on top of each page though. An idea I had would be to use js/css to make an overlay appear on the page that had the posting form.
>losin the *chan-ness of it by adding so many cookie-related options
:). Being "true" to the *chans is not a goal.
http://ochiba.x-maru.org/imgboard/newpost.html
This is what I've come up with. Thoughts?
Gee, imagine that - Internet Explorer chokes on both of those.
Appears to work find in Firefox/Win, though.
http://ochiba.x-maru.org/imgboard/newpost3.html
Now works in IE and Safari.
that is fantastic
Thanks. The Javascript/form portion was fun. The backend POST-handling is turning out to be decidedly unfun. But I should be able to put it in beta soon.
hehe, that's all im waiting for.. then i'm gonna megapost reply all your themed threads.
Or he could type "Anonymous". Sheesh.
If one believes that those wishing to post as Anonymous should have the privilege of not having to type anything at all, I would do it like this:
// Name is required
$_POST["name"] = $_POST["name"] ? $_POST["name"] : "Anonymous";
Just add that one line below the comment line at line 49 in includes/post.php
.
Waiting for the bitching about tripcodes next...
Err..
$_POST["name"] = $_POST["name"]=="" ? $_POST["name"] : "Anonymous";
Thanks for your defense, btw. I don't really want to be drawn into his holy war.
am i really daft or is there no way of doing this?
Nope. Administrative mistakes are not allowed.
Err... deletes are always tricky when you are using foreign keys, doubly so in ochiba because it's sqlite and I'm kinda fudging things. It's not so bad if you have FEATURE_MULTIPLE_CATEGORY set to false, since the images.category column will only have single values.
The easiest way is to first recategorize any images in the target category to something else, then delete the category. So, something like:
sqlite> update images set category='/other/' where category='/deleteme/';
sqlite> delete from categories where abbr='deleteme';
If you don't have shell or don't have sqlite access, then you can wrap the above statements into a PHP file, upload it, then "open" it. Something like:
<?php
require("conf.php");
$db = sqlite_open(DB);
when there is no space on the drive where /tmp resides, users get verification mismatch all the time.
i wouldn't say this is an error in ochiba per se, but i thought you should know :)
Weird!
I was baffled at first, but now I think I know why. The verification code uses a PHP session. Session files are usually stored in /tmp (typically sess_092j3kl2lk34092j34lkj
or whatever).
So, there's nothing too worthwhile doing in ochiba about it :).
i'm not a super l33t h4x0r like the rest, and stuck on reseller hosting with cpanel and all that other 'dumb-me-down' webhosting stuff. i've tried to make a /tmp/ochiba-cache in root and it still fails. is there a way to disable that cache thing, or is it dependent?
well, i got past that, but now just realized my host isn't sqlite-enabled. poo.
any plans for flatfile or mysql support?
No flatfile support planned. I don't know how that would be done.
No MySQL support planned, either. I don't use it and was hoping someone would contribute a MySQL-ified version of functions.php.
I want to try my hand at Postgres, though. Not that that does you any good.
I realize it's probably not a realistic option for most people, but I recommend looking for hosters that offer PHP5 (ie with built-in SQLite support). This will become more and more common, and was one of the reasons I used SQLite.
well, i've asked a few already, and they say php5 isn't stable yet. so i guess once that happpens, i'll hop on.
i also tried installing sqlite on a different hosting account of mine (on dreamhost), i 'think' i got it in right, but install still fails. not that i'm buggin, i'll probably have to ask an sqlite forum anyway.
I'm curious - how are you trying to install sqlite on the dreamhost server? By uploading a binary sqlite.so local to your account and using dl()? What kind of error (if any) do you get? The install.php script is a quick hack and isn't graceful about the different hosting circumstances.
If you are doing the local sqlite.so method, what does the following return?
if( !(bool)ini_get( "enable_dl" ) || (bool)ini_get( "safe_mode" ) ) {
echo "Loading extensions is not permitted.\n";
} else {
echo "Loading extensions is permitted.\n";
}
(stupid wakamark)
actually, dreamhost allows ssh, so i just did the ./configure and ./make, and it all went through, i suppose. i don't know what else i should be doing.
Aah. Then, copy modules/sqlite.so into the ochiba root directory, and in index.php put dl("sqlite.so")
and cross your fingers.
Unable to load dynamic library './sqlite.so' - /lib/libc.so.6: version `GLIBC_2.3' not found (required by ./sqlite.so)
no good, doh. i guess i'll wait if someone makes a mysql conversion.
Drat. They must have safe_mode on or something.
Have you contacted them, requesting either the sqlite module for PHP4 be made available if they are unwilling to provide PHP5 at this time? Even if they say "no" to you, if there are enough requests, they may do something.
Googling "PHP5 hosting" turns up a fair number.
i had problems installing, the install.php seemed to halt when trying to create the database (halted at "Installing database ...").
but i quickly found the cause in the logs:
Jan 4 11:26:32 delirium apache2: PHP Fatal error: Call to undefined function: sqlite_exec() in /path/to/install.php on line 75
and lookie it says so here:
http://se2.php.net/manual/sv/function.sqlite-exec.php
it's actually just in cvs? weird. maybe you should use sqlite_query() instead? i changed it to that and it worked just swell.
further on.. it seems i can't add a category. the query submits but the page goes blank and no category has been added. hmm.
right.. found i in functions.php - and it's sqlite_exec() doing its thing.
will something break if i change all sqlite_exec()'s into sqlite_query()'s?
hmm. everything else is smooth tho. great stuff! :)
hmm.. lastly, the imagerotate() function seems to be a bother to get working. got the rest of gd working ata least (i think? :)
now i've got it running though!
> Call to undefined function: sqlite_exec() in /path/to/install.php on line 75
Hmm. sqlite_exec() is relatively new, but if you get the latest PECL version (1.0.3), it should include the function. Nevertheless, I don't think using sqlite_query() in it's place will break anything (knock wood)- it's used in queries that don't return a result set (update, deletes, inserts).
> the imagerotate() function
Hmm. Never occurred to me that people would want to rotate after posting. I'll put it on the to-do list.
you're using imagerotate() when creating the verification image already! and that broke because..
http://se.php.net/manual/sv/function.imagerotate.php
> Note: This function is only available if PHP is compiled with the bundled version of the GD library.
:/ so i have no rotated verification text
Oh yeah, there :).
Did you build your own PHP? If so, you can just add "--with-gd" to the configure line. It's bundled into PHP>=4.3, so no external libraries have to be separately installed (other than libpng and libjpeg).
If you got a binary build, perhaps there's an "php-gd" package that is an apt-get away.
Otherwise, you can leave out just the imagerotate() call- it might work, it'll just be easier to machine-read. You might want to fiddle with the font selection in the imagestring() call to select a "better" one.
Hi,
This looks interesting, however I'd like to have the option of generating a conventional album (n x n array of images). Can Ochiba do this or is it strictly vertically organised as in the demo?
It's not currently possible, but I've been thinking about a more "2D" layout as well. I don't know if a strictly grid-like layout is appropriate for ochiba as the emphasis on thread-like discussions is an important part of it's goals (and a vertical orientation follows), however, perhaps as an alternate "collapsed" mode.
If you have any ideas, I'd be glad to hear them.
This forum is for the discussion of ochiba.
If a screenshot will be beneficial, post to the ochiba sandbox <http://ochiba.x-maru.org/imgboard/screenshots> and reference the post number.
Here's a first for your FAQ... What does this error mean?
Checking for convert (/usr/bin/convert) ... FAILED
I believe it's ImageMagick... I go (re)install it and se if that fixes anything.
Checking permissions on /tmp/ochiba-cache ... FAIL - COULDN'T WRITE
But the second bullet in the "Quick Start" section tells me to create a directory named /tmp/ochiba-ochiba, not /tmp/ochiba-cache...
> Checking for convert (/usr/bin/convert) ... FAILED
Missing convert, from ImageMagick. If your install places it elsewhere, you can change the path in conf.php and install.php
> "Quick Start" section tells me to create a directory named /tmp/ochiba-ochiba
Sorry sorry, typo, should be /tmp/ochiba-cache by default.