Posts by Dani

Funny.

Testing ...
testing ...
1
2
3

Will affect all future posts from now on :)

Hehe, cool! :) If you'd like, you can document your progress with a blog @ http://www.daniweb.com/blogs/

Awesome, thanks!

isorry about the indentation

Indentation works when you wrap code in CODE tags ;)

Hi! Welcome

Hi!

Hi

You can do this without any hacks via javascript by utilizing the external.php?type=js

If you want to have recent posts via php on a non-vBulletin php based page, I'm pretty sure the hack already exists somewhere on www.vbulletin.org (99.99% positive, actually)

Hehe ... you just resurrected a two year old thread.

Yeah, unfortunately you do lose a percentage of your members who don't have email handy when they want to use your site, or so forth. However, in the long run, it's essential to keep a large community tamed.

By default, vBulletin is only capable of sending out plain text emails. You will need to hack your vB in order to get it to send out pretty print emails.

The first thing you might be interested in, for vB 3.5, is the Community Bulletin plugin: http://www.vbulletin.org/forum/showthread.php?t=66334

The other is a hack which lets you send HTML emails from wthin the admin control panel: http://www.vbulletin.org/forum/showthread.php?t=99910

Good luck!

If you have an existing site, I take it you already have a webhost. One of the most popular beginner forum software out there is phpBB which you can get from www.phpbb.com - it's free and just requires a webhost which supports PHP and MySQL. It also comes with easy to install instructions.

However, you cannot have the "build it and they will come" mentality. There are 10000 other forums out there about any particular topic. With dedication and devotion, you can just about make anything succeed!

Yup, same collection as me. :)

Right beneath the tutorial, but above the ads, click the link that says "Write and View Comments on this Tutorial" and it will take you to the tutorial's forum thread.

The tutorial pages are really just a database pull of the first post of each thread in a hidden tutorials forum.

On second thought, you ARE looking for the edit button from the forum page of the tutorial, right?

http://www.daniweb.com/techtalkforums/thread47392.html

as opposed to

http://www.daniweb.com/tutorials/tutorial47392.html

I am really confused. As a regular member, you would have the ability to edit your post for a half hour since it was initially posted. However, you're a moderator of the entire Software Dev category, which includes Python. Give me a few to look into this ...

I see ...

Last edited by vegaseat : Yesterday at 10:21 PM. Reason: Added zip file

??

Hi

Hi, welcome!

I'm here! I'm reading this! Welcome :)

I send out my monthly newsletters Tuesday early afternoon. It's late afternoon by the time all 85,000 members receive the email. Still ... I think you should just play around with different days and times until you find the one that performs the best for you. I think the only conclusion everyone here has made is not to send it out on weekends, and yes to sending it out in early/mid afternoon.

Use DiskWarrior. That's my answer to everything.

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

http://www.daniweb.com/code/snippet68.html

Spam is unsolicited email. The definition of 'unsolicited' is anything not asked for. Whether the person may be interested in it or not, it's technically spam if the user didn't specifically request it, such as by opting into a mailing list or newsletter.

Hi, welcome!

Hi :)

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?

Sorry *blush*

Try posting in our Website Reviews forum for feedback about your site, if you haven't already done so.

Glad ya got it! :)

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?

hehe :)

Hi!

Hi! :)

Hi, welcome.

Hi! :)

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

Really? Please ... suggestions ... tell me ... :)

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?

haha

I really don't want to introduce a section devoted to gaming because it will inevitably attract a much younger crowd, especially for an IT community which is swaying towards the business end. However, feel free to chat up a storm in the Geek's Lounge!