February 23rd, 2002

inside toaster
  • pinrad


Everything is fixed now, and the database is populated. The httpd.conf file has the necessary directives. Now, when I access the site where I installed the lj server, I get an HTTP 403 error (forbidden). I tried "chmod 755 htdocs", even "chmod 777 htdocs" and I still get the error. I even tried adding a "Directory" block with necessary Options, still resulting in the 403 error.

Any help would be greatly appreciated.
  • halkeye

Edit info yet again

Sorry if i'm being a pain, but really trying to push this to get done.
I now have 2 version of the merge..
First usng mart's modified auth_fields_2 function to link to uploadpic.bml (here)
Second one is using the current ?authas= schema (here)

I think i've covered just about everything to date, problems and new patches.
Let me know if anything else comes up.

(as always, test at http://lj.halkeye.net/ with the test account)
  • halkeye

Support System Override Viewer

Next up we have a tool for the customization support people. It adds another row (as well as fixes a style issue todo with see_request) listing weither or not the user has overrides, and if they do, it has a link to a new page showing the overrides.
If the user is a paid member, then the support team must have privs.

I've address the issue with privacy (somewhat), and elimited the userid and replaced with just user.

The only code i'm not liking, at least for readability is:

+ if ( LJ::get_cap($u, "paid") || LJ::get_cap($u, "perm") ) {
+ return LJ::bad_input("You need supportpriv to see the overrides of paid members") unless (
+ LJ::check_priv($dbs, $remote, "supporthelp", "customization") ||
+ LJ::check_priv($dbs, $remote, "supporthelp") );
+ }

So if someone could suggest something better, let me know.

I got the customization people to test things, and they claim everthing is working (as per 24153883)

Patched files:

Created files: