Posts by Dani

Enable authentication on your SMTP server so that anyone can't just use your mail server to send out email.

Don't send out a doctype until you do your redirects.

Don't worry - I'll have you using it in no time :)

[search]dijkstra's algorithm[/search]

You gotta love our new search bbcode :)

IRC isn't that old school when it's all integrated into DaniWeb :) Our chat page shows which members are logged in, you can visit a member's profile to see what channels they are op in, what channels they're logged into, etc.

We already have an IRC chat network here.

http://www.daniweb.com/chat/

Every member can create their own channel, or chat room.

Ah, gotcha :) I guess we're all having bad reading for comprehension days today!

Yes, it does ... there was some confusion in mods incorrectly thinking he was hijacking that thread when he wasn't, and so he posted as a new thread. (You can read this thread for the full scoop = http://www.daniweb.com/techtalkforums/thread62507-2.html)

Yep, Got the point...

I still got the doubt on this .. So let me as well post it as a new thread.

Thanks for the advice..

bye

I was talking to WaltP :) We're all trying to apologize to you and tell you that you did nothing wrong.

It's okay this time, but if it happens again, I'm going to have to sick Dave's wombats on ya. And you KNOW he has a lot of those critters!

Careless I was :lol:
Thanks for the help you guys, I finally finished my project!

Let's make this more interesting...

Yes- responses to a thread should be directly related to the original poster's question/problem. Tangential postings only sidetrack the issue.

Let's get back on-topic.

<Dani takes off admin hat> But the original thread starter finished his project already, so there's no harm still discussing the topic and letting things into a deeper conversation about it. (Since the original fella was already helped, afterall) I've gotta convince you to stop thinking of the forums like a support ticket system and lighten up by letting conversations flow naturally. ;) :p :cool: <Dani puts admin hat back on>

Because what happens is people post questions, get replies, and then edit their original post deleting the question and replacing it with "Oops, my mistake! It was a dumb question, I figured it out myself." Additionally, sometimes members who have a grudge (they received a temporary ban, they had a disagreement with a moderator, etc) will react by editing all of their previous posts deleting their content in spite.

Because specifying an offset isn't available with a DELETE query as it is with a SELECT query. You can see the correct syntax for the DELETE query here:

http://dev.mysql.com/doc/refman/5.0/en/delete.html

Replace

<script language="JavaScript" type="text/javascript">
<!--
function checkAllOptions(){
 var file_01 = document.getElementById('file_01');
 if (file_01.value==""){
  alert('Please select a file to upload in Step 1 !');
  return false;
 }
 
 var file_02 = document.getElementById('file_02');
 if (file_02.value==""){
  alert('Please select a file to upload in Step 2 !');
  return false;
 }
 var file_03 = document.getElementById('file_03');
 if (file_03.value==""){
  alert('Please select a file to upload in Step 3 !');
  return false;
 }
 
 var file_04 = document.getElementById('file_04');
 if (file_04.value==""){
  alert('Please select a file to upload in Step 4 !');
  return false;
 }
   
 var email = document.getElementById('email');
 if (email.value==""){
  alert("You have to provide an email address !");
  return false;
 }
 
 return true;
}
</script>

with

<script language="JavaScript" type="text/javascript">
<!--
function checkAllOptions(){
 var file_01 = document.getElementById('file_01');
 if (file_01.value==""){
  alert('Please select a file to upload in Step 1 !');
  return false;
 }
 
 var file_02 = document.getElementById('file_02');
 if (file_02.value==""){
  alert('Please select a file to upload in Step 2 !');
  return false;
 }
 var file_03 = document.getElementById('file_03');
 if (file_03.value==""){
  alert('Please select a file to upload in Step 3 !');
  return false;
 }
 
 var file_04 = document.getElementById('file_04');
 if (file_04.value==""){
  alert('Please select a file to upload in Step 4 !');
  return false;
 }
   
 var email = document.getElementById('email');
 if (email.value==""){
  alert("You have to provide an email address !");
  return false;
 }
 
 return true;
}
-->
</script>

Notice how you opened the <script> tag with <!-- (which is an HTML comment) but you forgot to close it before ending the </script> tag. Therefore, IE thinks that the entire page is just one big HTML comment with …

Hmm yeah this thing has even happened to me quite a number of times..

Which browser you use Mr. Andor, i use Firefox ?

Sometimes this can happen after using the Quick Reply box, since it uses AJAX to add your post to the bottom of the thread list without refreshing the entire page. A page refresh should normally fix this.

Hmm ... I can't reproduce this error. Does anyone else see it? It looks as if in Firefox you are logged in but in IE you are browsing the site as a guest. Do you maybe have me in your Ignore List?

I think it's because of the AJAX call when you used the quick reply box. Can you reproduce the error upon refreshing the page?

Because avatars are static images that get uploaded to an avatars directory where they're hosted. In order for the certificate to remain up to date, it must be hotlinked.

Ah nice didn't know that it exist

It was just added yesterday, to do [code=language] where language is anything within our code snippet library.

Actually, you can now use [code=c] :) Tags added for him.

Internet Explorer 7 is actually out of beta. If your computer restarted midway through an install, I would go into Add/Remove programs and do a Repair on the installation of IE7.

Welcome!!

definition of syndication: The process by which a web site is able to share information, such as articles, with other web sites.

You can syndicate DaniWeb information by posting your member badge on your website, using our RSS feeds through a newsreader, or posting teasers to our articles on your website.

His only way out of poverty, Wolfy :-P

I'm sorry to hear all of that. Are you sure you didn't accidentally infect yourself with some type of virus or trojan which just started acting up now?

... at where?

Please take what I have to say with a grain of salt, as this totally isn't my domain. However, what would happen if you left the battery in your laptop, and plugged in the AC adapter, leaving the computer off. A little while later, unplug the AC adapter, and boot the computer off of the battery, and see if the AC adapter recharged the battery at all while the computer was off.

Yell at vBulletin.

Use PHP-tags instead of CODE-tags

We're upgrading to a new version of vBulletin within the next day or so. Once the massive upgrade is complete, and big bugs are fixed, things like this will be looked into.

In the meantime, try switching between the standard and advanced wysiwyg editors.

Are you using the horizontal scrollbar near the bottom of the post?

nightwishmaster is helping me to strengthen the community aspects of the site, which I've been trying to work on improving lately.

Testing ...
testing ...
1
2
3

Will affect all future posts from now on :)

isorry about the indentation

Indentation works when you wrap code in CODE tags ;)

Use DiskWarrior. That's my answer to everything.

What, no ooohs or ahhhs about my caching system that I ingeniously thought of and implemented?

Yes, it would *blush*

Essentially ... the database contains two post tables. One of actual posts, and a second of recent posts that have already been parsed (had their bbcode turned into html so they're ready for output). This eliminates the overhead of parsing bbcode on the fly.

However, there is still the overhead of having a JOIN clause in all of the SQL queries from the post table for the post_parsed table. Additionally, as new posts are viewed, the post_parsed table needs to get populated on the fly.

What I actually went ahead and did (and have been working on) is replicating this post_parsed table within the filesystem. This eliminates the need to do a join on the post_parsed table when doing a post sql query (and because both of these two tables are enormous, it alleviates strain on the database server). Additionally, because two versions of each post (parsed and not parsed) now don't need to be sent back, the bandwidth between the web and file servers is reduced. It also reduces the number of queries on each thread view by one because the post_parsed table no longer needs to be updated for new posts that haven't already been its cache. Additionally ... because I am now storing each parsed post as its own .php file in the file system, eAccelerator (which stores compiled versions of php files in ram) picks up on all of them. What this means is I'm essentially storing parsed, ready-for-output …

Can someone confirm?

Testing ... test\ing ... 123 ...

Update ...

cout << "test\n";

Another 'test'

Eeek ... Okay, I will look into this ... I know what the problem is. I was working on coding a post cache.

It works for me just fine in IE 6 / Win XP and in FireFox / Win XP and in Safari / Mac OS X. Can anyone else confirm?

I'm really confused by what you're talking about?

Well I spent most of yesterday coding the cache so its code is still fresh in my mind.

See how it now shows your post was initially created at 6:07 and you edited it at 6:08. Before now, the database wouldn't have bothered recording that edit or displaying that notification on your post.

I think this is a small price to pay for my cache. Besides, as a forum reader, sometimes I do happen upon a post within the first minute or two after it was initially written, and I would like to know if there was a typo that someone fixed or such.

Like I said ... I am using a combination of the postid and the time the post was last edited to uniquely store each version of a post in my new handy dandy cache.

However, I had a vBulletin option enabled to not record edits made within the first 5 minutes after a post is initially created. Therefore, when you were editing your posts, the database wasn't recording that there was an edit. Therefore, a new version of the post wasn't cached, since it didn't know there was an edit made.

I've changed this to now record ALL post edits regardless of if they're made 1 second after the initial post is created or 1 day after.

Okay, I figured out the problem.

<< edit: Just testing ... >>

Oh my goodness! It just happened to me! ... Looking into it ... it's strange because I'm saving the cached versions with names that are a combination of the post ID # and the last edit time, to (supposedly) accomidate post edits.

I spent a lot of time yesterday playing with creating a caching system that stores preformatted versions (ie parsed bbcode into html) of recently viewed posts in RAM on the Apache machine, to not only eliminate a query to the database server, but also eliminate having to parse all posts on the fly (in real time). The problem you're experiencing did indeed happen for about an hour or so yesterday while I was working on it. It should be fixed by now though. Can anyone else confirm?

Does the file have global execute privileges?

Make the last line of the script run the script :)

Oh, I'm sorry. I confused the answer to your question with the best way to get runaway processes.