Hello all,

Having upgraded to K2 2.7.0, I am encountering a 500 Internal Error which doesn't seem to appear in my error logs.

Is there any way I can track this down? Is there a K2 error log? Or has anyone else experienced this?

You can see the error in action by viewing any page from within K2 on my site, such as:

quid.org.uk/all-ongoing-projects/on-going-projects
quid.org.uk/all-completed-projects/completed-projects/item/55-buckle-fractures-of-the-distal-radius-increased-efficiency-and-cost-savings-through-a-new-management-pathway

Other components, like JEvents, are working fine.

Any help appreciated!

Alan

I have same error. Also an error in k2 is shown: imgur.com/3m2fqYH

Any idea?

Thanks in advance.

BR,
Víctor.

That error looks like a poorly formatted missing fields error - is that from your submission form?

Have a look at the source of that page output and see if it mentions missing/required fields.

Still none the wiser as to the 500 error.

meta description tag, takes the description in the category !!!! headers are not implemented for the materials. The rest of a lot of good improvements.

Sorry, I don't quite understand what you mean - please could you clarify?

This error happens when i add a new item or update one (also without changes, only "save").

The code has

<!-- Required extra field warning -->
<div id="k2ExtraFieldsValidationResults">
<h3>The following fields are required</h3>
<ul id="k2ExtraFieldsMissing">
<li>Loading...</li>
</ul>
</div>

I don't understand what happen; i only upgrade joomla and k2 extension.

Thanks!!!

BR,
Víctor.

Viktor,

I'm definitely no expert but it just looks like the standard required fields error.

Put a dummy entry into all your fields and see if it accepts it. If so, you'll need to go into the extra fields in K2 admin and toggle the fields from being required to not.


Anyone any ideas about this 500 Internal Server Error post-2.7.0-upgrade issue? Anyone having it come up in their server logs? It's likely a simple permissions error but with no log I can't fix it.

Alan

Thanks Alan!!!!

Indeed, the problem was an "extra field" I do not know why it has become a mandatory after updating the version. Sorry for the inconvenience. Many thanks.

BR,
Víctor.

Hello to all,

Please look at this post: www.joomlaworks.net/forum/k2-en/45145-solved-error-after-upgrading-to-k2-v2-7-0#152643

@Alan,
Can you paste the exact error? You might need to enable error reporting to see the actual issue.

Dear Krikor,

I've tracked down the issue: the PHP module mbstring wasn't functioning properly. I found this by running a diagnostic script looking for PHP modules that Joomla is dependent upon.

This just required a server reboot - so not a K2 issue. However, I wonder whether the K2 admin panel could have a check script that warns if this or other server problems are the cause for the issue?

Thanks for getting in touch and I hope this helps some people.

(For some reason, my server wasn't logging the error - beyond me why, so I've sent a support request to my host!)

Alan