just stopped working?  what changed?  something must have…

take a look at the forum – toolbox – error log admin panel and please tell us the entire error message…  best to look right after trying to view pms…

paste the message here, but please do not at this time post and php notices you might be seeing – just want warnings or errors…

Steve, I have no idea what happened…

The error log is full of stuff!

Here is what I see re.errors.

The following dB tables do not exist:

wp_sfpmthreads

wp_sfbuddies

wp_sfpmrecipients

Also something else happened!

I have a file sp-plugin-styles-all.css completely custom. Everytime the forum gets updated, I overwrite that file with mine and everything works fine.But now something changed…

Looking at Firebug, I noticed that the css comes from wp-content/sp-resources/forum-cache/

So I have overwritten that file as well, but nothing changes. Also, in Firebug, the link is wp-content/sp-resources/forum-cache//sp-plugin-styles-all.css

Where is that double slash coming from?

Private Messaging

So it looks like when you activated/updated the PM plugin then it was unable to create the necessary new tables. And that is a little worrying. I assume you have current messages in your database that are wanted so we can’t uninstall it and start again. I will need to do some tests and talk to Steve regarding the best way to force the upgrade of PMs to have another go. I believe this is the only report we have of this so it is curious as to why the upgrade failed to run…

Combined CSS Cache

We did indeed relocate this as it had become apparent that placing it directly under the wp-content folder was not an option for all users. Your double-slash issue is also a unique report to the best of my knowledge. Again – I will have to ask around here to see if there are any ideas but I suspect external influence in some way….

Thank you Andy!

All the PMs have been lost, but that’s not a problem. The problem now is, it’s not possible to send a PM!

It says “Unable to create a new PM thread”.

As for the CSS, is that file somewhere else, apart from wp-content and sp-resources/cache?

The existing PMs should not be lost. They are just currently inaccessible.

No the CSS file is only held in that one location. But that is a good point. Go to the forum admin > Integration > Storage Locations and check the ‘forum-cache’ folder. Is it held in there correctly? No slash ion the end?

No trailing slash at the end, Andy.

As for the PMs, I uninstalled and reinstalled the plugin once again and now it’s working!

All the older PMs are gone, but that’s fine.

Now I need to fix the problem with the damn CSS file…

Ah yes – uninstall will remove all the old ones I am afraid. But still – if that is OK at least it gets you back working.

I have left a note to ask Steve about the CSS file issue but am still thinking it might be an external thing. Anything installed that might be effecting url’s in this way/

why do you overwrite with your own version of a cache file? risky at best…  its a generated file and could get recreated as needed…

as Andy says, the location was moved and is now controlled on the forum – integration – storage locations…

the // issue was introduced during the move and already has been fixed for next version (Andy was on vacation and missed the ticket/fix)…  but its harmless…  the // directory will be the same as a single slash directory…

so not really sure what css issue you are having (apart from overwriting a generated file – risky)…

Steve, that CSS file is located in the wp-content folder.

I used to overwrite it after each upgrade and it was working perfectly.

I have tried and delete the one created in the cache and the system generates it again as it should, but it’s not like the one I have overwritten in wp-content.

Pretty strange…

Could W3 Total Cache be involved somewhat? I had W3TC up and running even before and nothing ever happened…

Guys, I use an example.

In both files located at wp-content and sp-resources/forum-cache, there is:

#spQuickLinksForum width set as 203px

But the system is using 230px. Firebug reads the cached file. So where that 230px comes from?

It’s driving me nuts!

the css file will be wherever you have it located at on forum – integration – storage locations…

if you have in another location, it will not be used…  if you are letting w3tc cache the forum page you will have issues… you need to tell it not to cache the forum pages for all types of caching in use…

I still dont understand why you are manually overwriting the cache file… why use the css caching then?  you can disable it on forum – options – global settings…  you can also clear and reset the cache on forum – toolbox – housekeeping…

what is link to site?

Steve, I looked at everything.

W3TC do not cache the forum page.

I went to toolbox-housekeeping, and clicked Reset combined CSS cache.

Nothing changed!

I am sendong you a PM with a login, because the forum is closed to general public.

this file:  http://www.xxxxx/wp-content/sp-resources/forum-cache/sp-plugin-styles-all.css

this file clearly has the quicklinks width set to 230px…  I can open the file and view it… so not sure why you think 203px.

that file is auto generated, so hand editing is a bad idea… 

you are also serving cached pages…

<!– Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk
Page Caching using disk: enhanced (Requested URI is rejected)
Database Caching using disk (Request-wide User is logged in)
Object Caching 8053/8069 objects using disk

 Served from: xxxxxxxxxxxxxx @ 2013-11-06 17:10:38 by W3 Total Cache –>

and should resolve that (yes, page and db rejected here)…  minification could lead to errors since our files are already minified…

Steve, I switched off W3TC and nothing changed.

Regarding the files, the one in wp-content has that width set to 203px. So why is the one in sp-resources/forum-cache set to 230?

This is what I do not understand! They should be exactly the same. Am I missing something?