[Curtis Thompson]

hello…

not really, no, outside of the traditional ones like not using neon and that sorta thing…usually sites will play off of some complimentary color to their logo – that’s a great place to start…

sitruc

[Curtis Thompson]

hello…

this has been a long-time belief of mine, but i still say that if you want to study anything about the web, you should start at the source. if you want to get very technical about stuff like the 216 color palette and theory and that sort of thing, then there are certainly books that will tackle that for you, but if you just want to see what good design is, you have the world at your fingertips (literally)…try some inspiration sites like:

https://www.cwd.dk
https://coolhomepages.com

if you browse there. you’ll see a bunch of really cool design that might get the creative juices flowing…and on a plus side, it’s free…

sitruc

[Curtis Thompson]

hello…

not really – there are a mess of server variables that you can use like SCRIPT_NAME, REQUEST_URI, etc…you can grab them all with getenv:

https://us4.php.net/getenv

try making a page with phpinfo() to see all the environment variables that you can use…there is likely a path in there that you can make use of as a url path there so that you won’t have to change it between templates…

sitruc

[Curtis Thompson]

hello…

hfs+ does not have the 2gb file limitation, so that is not your issue…

one thing to try is to open a command prompt and see if you have any file size limits set – under bash, it’s:

ulimit -a

and under csh it’s:

limit

check the filesize param – it should be unlimited, but perhaps you have a limit?

just a guess…but it’s not your format type if it’s hfs+…

sitruc

[Curtis Thompson]

hello…

ya – that’s an odd one! i think the easy way around it would be to make the background image url include the relative path – so instead of BACKGROUND=”menuimage.jpg”, try BACKGROUND=”/path/to/menuimage.jpg” – then safari might recognize them as different images…

sitruc

[Curtis Thompson]

hello…

if you have traffic and visitors willing to post, then having your own forum is nice because you can use it to show people that you know what you’re talking about – good resume material…but having a dead forum is pretty useless, and as you note, there are a lot of forums out there, so just putting a new one up won’t likely result in the desired traffic…

promoting a forum is hard – the best way would be other forums, but you’ll get banned if you go to somebody else’s forum and try to get people to come to your own…so it’s sort of a chicken/egg thing, unfortunately. forum traffic is often built by either word-of-mouth or advertising, so those would be the best way to go about it. but it’s hard even then because if somebody comes to a dead forum, they’re likely to not post…so you’d have to build it up with colleagues and friends first to make it look alive and then start trying to get the word out…

sitruc

[Curtis Thompson]

hello…

odd but could be your culprit:

https://www.mredkj.com/tutorials/tips_ie.html

sitruc

[Curtis Thompson]

hello…

perl can certainly do this, or pretty much any scripting language. the end result will be the same as if you were to link to a file that your browser doesn’t recognize – you’ll get a (on ie/windows anyway, other browsers with download managers will likey just grab it anyway) open/save/cancel dialog and then the decision can be made as to what to do with the file.

but if your browser recognizes the file, it will display it inline (so like if you linked ot a jpg, then your browser knows all about those) and won’t offer a file dialog, but rather it will just display it on its own. the way to get around this is to stream the content as an “application/octet-stream” or (“application/x-download” – either one will work) mime type, which the browser will then just hand on to the user’s system and it will deal with the file…

php is really equipped to do this – here’s a sample from their docs:

// open the file in a binary mode
$name = “.publicdevimgok.png”;
$fp = fopen($name, ‘rb’);

// send the right headers
header(“Content-Type: image/png”);
header(“Content-Length: ” . filesize($name));

// dump the picture and stop the script
fpassthru($fp);
exit;

so you could just switch the Content-Type header to “application/octet-stream” instead of “image/png” and you’d be good to go. you can also get much fancier and only allow the users to download certain file types (good idea regardless), and then create a hash (array) of mime types to extensions…

perl can do it the same thing – here’s a tutorial on that…php sorta grew out of perl and unix, so a lot of the php above will look very familar to this perl code:

https://www.sitepoint.com/print/file-download-script-perl

hope that helps! lemme know if you have any questions…both these ways are nice because before streaming the file, you can do any code you want to verify the user (check session in php, ip in either, etc.)…

sitruc

[Curtis Thompson]

hello…

not experiencing that in my ie here with a similar build – is this happening with every site? and what happens when you choose the view source item from either the top menus or the context menu?

sitruc

[Curtis Thompson]

hello…

whatever your form action is in the form is where you’ll find your variables – so if it’s a post method form, then they’ll be in either _POST or HTTP_POST_VARS…probably the latter in 4.x if i recall correctly…

sitruc