Error when deleting categories

[Shades.]

I tried deleting a forum category and received the following errors:

Warning: require(/home3/******/public_html/biker/cache/data_54087f6b62ad05f8171418bd9da93d54-SMF-modSettings.php) [function.require]: failed to open stream: No such file or directory in /home/******/public_html/biker/Sources/Load.php on line 2736

Fatal error: require() [function.require]: Failed opening required '/home3/******/public_html/biker/cache/data_54087f6b62ad05f8171418bd9da93d54-SMF-modSettings.php' (include_path='.:/usr/local/lsphp5/lib/php') in /home/******/public_html/biker/Sources/Load.php on line 2736

But after refreshing the page the category was removed and the board is working fine. What is causing the above error and how do I fix it?

[CapadY]

Did you have this error only once ?

If it is continuing this error just empty your forumcache, I think that will solve it.

[Shades.]

It's been happening several times. Every time I try to add or remove something I get that error or a similar error. I just emptied the cache so will see what happens.

I'll mark this topic solved for now!

[Shades.]

Ok, I emptied the cache several times and am still getting those errors. I also get those errors after posting and editing on the board.

[Shades.]

Error logs are showing this:

2: unlink(/home/******/public_html/biker/cache/twitter.lock) [<a href='function.unlink'>function.unlink</a>]: No such file or directory

File: /home/******/public_html/biker/Sources/twitter.php
Line: 978

I guess I need to post this in the Twitter mod support thread too!

[CapadY]

The only thing you can try is disabling caching and clearing your forrum cache once again.

[ɔɔɔɔɔɔuɥoɾ]

Error logs are showing this:

2: unlink(/home/******/public_html/biker/cache/twitter.lock) [<a href='function.unlink'>function.unlink</a>]: No such file or directory

File: /home/******/public_html/biker/Sources/twitter.php
Line: 978

I guess I need to post this in the Twitter mod support thread too!

Clearing your cache will not really do anything here, I just saw this myself, the problem is that the twitter.lock is not been cached in the 1st place, and the file cannot be located.

Definitely a question for the twitter mod author.

[JimM]

I suspect that all your errors are being caused by modifications as "SMF-modSettings.php" is not a file that you will find in the package.