Posting problems (16)

1 Name: forceflow2 2005-09-13 21:36 ID:5CCsvzg4 [Del]

I am having some problems getting Wakaba running. I can't seem to get posts to actually post. The perl scripts can execute and everything, but it just displays a blank page, doesn't reload the image board, and the post is not added to it. When I looked at the database, it doesn't have any tables inside it like the script is supposed to create. I don't really get any errors anywhere from what I can tell. The MySQL password and everything is correct and the database does exist.
I'm using Apache 2.1.7, MySQL 4.0.26, Mod_Perl 2.0, Perl 5.8.7. Any clues?

2 Name: forceflow2 2005-09-13 22:11 ID:5CCsvzg4 [Del]

Ok, the tables got created this time, but the same thing happens.

3 Name: dmpk2k!hinhT6kz2E 2005-09-13 22:29 ID:10R2HoA2 [Del]

What do you see when you do a select * from comments? Have you downloaded wakaba.html through ftp (or used less in the shell) to look what's in there? What happens if you refresh your browser or use a different one?

It's probably a caching issue, either within your browser or an intermediate proxy. example.htaccess in the distro shows one way of offsetting broken or overly-aggressive cache behaviour.

4 Name: forceflow2 2005-09-14 00:25 ID:Yp6bAk8P [Del]

select * from comments gives me an "empty set"
wakaba.html shows the page correctly, just without any comments (which makes sense since there isn't any in the table)
Refreshing my browser browser did the same thing, but after I deleted my cache it didn't just stick on the blank page, it refreshed wakaba.html, just the comment I attempted to post didn't appear. Deleting the cache or using an alternate browser yields the same results. I guess that's progress though. Thanks for your help.

5 Name: forceflow2 2005-09-14 00:53 ID:Yp6bAk8P [Del]

Whoops, well, I accidentally deleted wakaba.html and now it is back to it's old tricks of not showing anything at all again when accessing and not regenerating wakaba.html

6 Name: !WAHa.06x36 2005-09-14 06:02 ID:3JfP6J52 [Del]

Go to http://.../ and rebuild caches.

7 Name: forceflow2 2005-09-14 10:43 ID:Gc9MzcbL [Del]

that just shows a blank page also but this time it generated an error in apache's error_log

[Wed Sep 14 11:31:16 2005] [error] Not enough arguments for ModPerl::ROOT::ModPerl::Registry::var_www_localhost_htdocs_b_wakaba_2epl::delete_all at /var/www/localhost/htdocs/b/ line 111, near "))"\nNot enough arguments for ModPerl::ROOT::ModPerl::Registry::var_www_localhost_htdocs_b_wakaba_2epl::add_admin_entry at /var/www/localhost/htdocs/b/ line 125, near "'')"\n

8 Name: !WAHa.06x36 2005-09-14 11:01 ID:9eKXLwHx [Del]

Hmm, mod_perl? I've never tried running with that. It may be that I have some function prototypes wrong and that normal Perl won't complain about it, but mod_perl will. It is easy enough to fix: Look up the functions mentioned, and look at the definition:

sub some_function($$$)
my ($arg1,$arg2)=@_;

In this case, the function takes two arguments (arg1 and arg2), but it is declared to take three ($$$). If you just jiggle around the prototypes until they're correct, it that might fix it. You can also remove the prototypes entirely for the functions that fail - they're only there for bookkeeping, and don't affect the functioning at all. For instance:

sub some_function
my ($arg1,$arg2)=@_;

I'll try to fix that in the Next Version, but that will be some time yet.

9 Name: Anonymous 2005-09-14 11:52 ID:qOTCs0OV [Del]

> It may be that I have some function prototypes wrong and that normal Perl won't complain about it

Normal Perl complains about it only with the "use warnings" pragma.

10 Name: forceflow2 2005-09-14 15:06 ID:hFsK9S/q [Del]

Ok, I got it to where it doesn't generate that error anymore, but that leaves me back to where I was before with wakaba.html not being generated and and if is accessed, it just displays a blank page. You mentioned you don't use mod_perl, I thought that was required to run perl scripts on apache? Thanks for the help.

11 Name: !WAHa.06x36 2005-09-14 15:10 ID:9eKXLwHx [Del]

No, Perl is usually run as CGI. Just add an Options +ExecCGIand AddHandler cgi-script .pl to the config, and make sure the script has execute permissions.

There are probably some mod_perl options you'd need to tweak to get it to work, but I know nothing of that.

12 Name: forceflow2 2005-09-14 15:27 ID:hFsK9S/q [Del]

Getting closer, I believe. Ok, removed mod_perl and just using execcgi now. The perl script is executable, and it redirects me to wakaba.html, but it isn't found (It tells me there are similar names and shows the, wakaba.js, and wakaba.ico as choices) Not getting any errors in my logs either.

13 Name: forceflow2 2005-09-14 15:37 ID:hFsK9S/q [Del]

YES! YES! YES! I went into the admin task and rebuilt the cache and now it works! Thank you so much! I would never have fixed this without you. Thank you, thank you, thank you!

14 Name: Anonymous : 2010-09-19 23:20 ID:x2YTQ1Ut [Del]

i'm having the same problem because the post form has no action, neither does the delete form, i've found this is a problem with "get_script_name()" but "get_secure_script_name()" still works because the "manage" link in the top right still works

here's what the post form looks like:
<form xmlns="" id="postform" action="" method="post" enctype="multipart/form-data">
i know this thread hasn't had a post in 5 years, but i need help

15 Name: !WAHa.06x36 : 2010-09-20 08:27 ID:Heaven [Del]

Don't run from the command line.

Also, rebuild caches.

16 Name: Anonymous : 2010-09-20 16:13 ID:sNnAGBXT [Del]

the problem was the $self variable wasn't working for some odd reason, so in, i replaced all instances of $self with get_script_name() and it worked
though passwords still don't auto-generate

Name: Link:
Leave these fields empty (spam trap):
More options...