Two little problems:

1) The glow is around the status icon as well as the user name. I've tried a workaround with no luck.

2) The gift images aren't showing up. Just a red X.

Thanks for your help!

re-upload the gifts folder from v1.1.8

I believe there was a "admin Donate" option in the options manager that had nothing to do with mass forums.

1 - If you have an icon displaying next to your username this is how it is supposed to work. Otherwise it will display the icon on the next line...under the name. There isn't a perfect scenario that is known about that will allow the username to glow while not making the icon next to it glow.

2 - The gifts thing has been discussed recently, and because of the problem with them, CMX has attached them to the post to download and then upload to your server. Look for them in the same place you download the hack.

AH crap. Sorry to mislead you. For some reason I quoted your post, when in fact they had nothing to do with each other.

My apologies.

U need to goto Manage Options -> Admin Donate -> and look at the bottom now for the settings. The redundant setting of "Log Purchases" was removed for the Bank, Thief & Donates due to there being an on/off for each item already.

I've redone the reset forums points now. The problem was it was setting the forum table values, but the datastore cache wasnt updated, now it should update it properly as well as the datastore cache. This update is in v1.2.0

Not at this time, its pretty advanced, but I tried to make it as easy as possible. Some options u can add urself easily, others u'll need to write an action.something.php file for.

1) You will not be able to fix this if you want the username and status icons to be displayed on the same line like..

Username - Icons...

Even if you hack your postbit template and put a </div> after the $post[musername], it will pust the icons down to the next line...

Username
Icons....

This is due to the way the Glow feature works and there will never be a way to fix this unless M$ changes IE's glow to NOT use the "display:block;" style. If you do not use an HTML command that has a block display, the glow will not work at all. So if u want to push the icons down, then edit ur postbit template some, otherwise, u'll have to cut ur losses and let the status icons glow too.

2) That is fixed in v1.2.0, the files are back to normal, reupload all files in the UPLOAD folder like always to fix this.

-CMX

CMX_CMGSCCC,

Just out of curiousity, is there any reason why you don't have an expire table that holds information on all items that have expiration dates? And then running a vbcron once every 24-hours set everything back?

Seems like that would cause fewer corruption headaches with the expiration field in the user table. And this would also allow items to expire without the user having to log in.

I think this method would be a lot more efficient than what you're currently using (although I suppose it would require an extra ADD query when a user makes a purchase).

The reason was, I didnt want to do any Cron Tasks at first, but now I have done 3, I guess a 4th one couldnt hurt...

I have finally fixed the problem that some users had with expiring options in the v1.2.0 release. In reality, an expired options table method would be much more effective because even if the item somehow got removed from a user's history, it would still be in the table of options to expire.

The main problem with expiring options is, some options can not expire at all, and/or require longer processes to expire. For example, if u wanted a username to expire and go back to the old username, that would create about 6 more queries to change per username that expired due to the fact it has to change the username in posts, thread, etc...

The current expiring field now makes it expire based on when the user is active and it calls the estore.php. The reason that is a good thing is, if there are "custom expiring fields", it would be easier to handle in the estore.php file instead of a cron task job...

So all in all, I really dont know which one is the "best" method to use. Each have their pro's and con's. And if a cron task is used, it would only be able to handle the "basic" expiring fields and as far as I know, cron tasks are basically ran soon as someone access the forums on a given time? It's not running the tasks like a real cron job is it? Meaning for example, if u had to expire 100 user options, it would do 100 queries for some user who happens to view it at the time it needs to run the cron task?

Correct me if I'm wrong about the scheduled task system as I havent taken the time to research it to see how it actually runs them. I'm just assuming it doesnt have 'root' access to be able to start a REAL cron job.

-CMX

I like it now with the "eStore Main" Link. Now it is perfect! Thanks

Wouln't it make sense to have another field option "Thief Reason" under "Thief"?

so far it appears the the newest release has cleared up all bugs for me, seems to be working wonderfully!! If I manage to get that error code again Ill let you know.

Thanks again for all the work you've put in, Ill send some paypal your way as soon as I get paid. Thanks bunches!!

Jo