Notifications
Clear all

wpForo 1.x.x Reply with attachment fails

12 Posts
2 Users
0 Likes
547 Views
ghutchnet
Posts: 21
Topic starter
(@ghutchnet)
Eminent Member
Joined: 1 year ago

When I did my first evaluations and test of wpforu I tested image uploads and they worked great.  I am unsure when they stopped working.

Reply
dimalifragis
Posts: 1920
(@dimalifragis)
Noble Member
Joined: 3 years ago

Ok, turn also on Wordpress debug ON and debug to a log to ON (true)

// Enable WP_DEBUG mode
define( 'WP_DEBUG', true );

// Enable Debug logging to the /wp-content/debug.log file
define( 'WP_DEBUG_LOG', true );

And when you do what it doesn't work, press (before) F12 and see your browser's console.

If all those are clear, then it could be a permission issue, ask your hosting company to see the real error and fix it.

 

Reply
2 Replies
ghutchnet
(@ghutchnet)
Joined: 1 year ago

Eminent Member
Posts: 21

@dimalifragis Any other suggestions?  I have run all of the clean up tools in the plugin, the debug area shows no database issues, I have removed many of the other plugins that I thought might interfere.  I have also tried a very small attachment to be sure the failure is not size related - it also failed.

Could the path to the WordPress install be an issue?  Could WPForo be having problems with the path when it's time to display the new topic?  As I stated, the attachment uploads to the host so permissions don't seem to be the issue.  Permissions for the upload area is 0755.  After the upload completes is when the internal server error message shows up.

Reply
dimalifragis
(@dimalifragis)
Joined: 3 years ago

Noble Member
Posts: 1920

@ghutchnet No. That error is cryptic and can only be explained by your hosting company (they have the full logs).

Reply
ghutchnet
Posts: 21
Topic starter
(@ghutchnet)
Eminent Member
Joined: 1 year ago

I have turned on WP debug and only got a few deprecated define errors in my theme.  Nothing that would indicate an error with attachment uploads.  It seems strange to get a 500 error and not see it in the WP debug error logs.  I suppose it must be a hosting error.  I will check there next.

Reply
Page 2 / 2