I have tried looking everywhere for an answer but i can only find references to Unknown Type errors, this seems to be different.
I have installed a nightly snapshot build of solr (apache-solr-4.0-SNAPSHOT.war) which i have had to do because the pdfbox library that comes with stable is too old and would not read them. but that's another story.
What i have at the moment is an error from php SolrClient::AddDocuments() with the error message from the exception as 'Unknown style "html"', please can someone explain what could be causing this error.
Thanks in advance.
This appears to be a difference in the structures of the config files. I edited the schemea.xml and solr-config.xml files and the error disappeared. Exactly what change made it disappear I am not sure as I amde several at once.
Thats the best answer i have.
Related
I'm a little lost here and didn't know where else to go so I thought best place to ask would be here... So, I recently upgraded my site's server from shared to VPS after which I attempted to download an Excel report from my DB like I usually would do regularly. However, since the upgrade after I download it, I get an error when opening the documents; it gives me the option to still open it but it is clearly corrupt or something. I have attempted to debug this issue but I am most definitely struggling with this one. I've also made sure I'm using the most recent version of PHPExcel but sadly this didn't resolve it. The error I'm experiencing is as follows:
The file format and extension of "myReportName.xls" does not match.
If anyone can shed a little light on what might be going on here I'd really appreciate it, and thanks in advance!
UPDATE: I don't think this would affect it, but I thought I'd add I also had a bug with my DB after the upgrade where nothing would insert due to fields not having a default value. They worked fine on the shared server but on the VPS I had to edit all my columns to have a default value of null. Also in case someone asks I didn't think it was necessary to post my code as it was working fine before the server upgrade so I thought the bug wasn't there, but if I'm wrong feel free to let me know.
Beginner question: I have done around 30 hours trying to sort out an error handler, essential as I am not a great programmer. I am 95% sure I can’t do anything about fatal-fatal errors but I am still 5% hopeful.
My error handler was working well sending out emails and text messages when it encounters problems but then I got an empty page with just:
Fatal error: Cannot use try without catch or finally
in /directory/ etc ...filename.php on line 999
(I had accidentally deleted the catch block.) The question: Someone somewhere mentioned htaccess 500 pages.
I did not understand what was described when I read it. I have done almost nothing with htaccess up to now.
Is there a way to trip some sort of static page? (I am 95% sure I can do nothing but I am stuck and still have a 5% hope and this is really important for me.) I am still running PHP 5.6 but do not want to upgrade to 7 yet. Catching these errors is far more important for me than the warnings, notices, deprecateds etc that I can catch.
Update
I saw that question and used some of the techniques there BUT it is 11 years old, huge, partly outdated and does NOT primarily address the problem I now want to solve.
I have no problem dealing with "fatal errors" such as calling a non existent function. My problem is about errors found when the script is parsed and are "unrecoverable". In my case a missing catch when a try is present.
The other answer, answers this in parts but not in ways that I can seem to use. I think there maybe a way of forcing a 500 error rather perversely by stopping error display which I will investigate soon/tomorrow. I would be grateful for 24 hours to check. I am quite happy for someone more knowledgeable to put up a better question/answer and useful info could be culled from that thread but, frankly it is a mess unsurprisingly after 11 years.
Answer - almost
Switch display_errors to off and you have a 500 error. Sadly I cannot get an .htaccess redirect to work (404 works fine). If you are good with .htaccess hopefully you will have some joy.
In some discussions there is talk of some 500 errors being "CORE" errors and REALLY unrecoverable even by .htaccess. My logs are very sparse and I cannot see any useful indication if this is the case for the catch when a try is present error.
(With a big thank you to #Dharman (if it works)). PS Will tidy this up when/if I get to the end of this.)
I don't think PHP can do anything with parse errors (or other errors during the compilation phase), but you should be able to configure your web server to display an error page of your choosing.
You don't say what web server you are using, but for example with Apache these are the Custom Error Response settings. Your errors will be HTTP 500 errors.
im using joomla3 for my new site , i used 3.2.2 and currently update to 3.2.3. but its always giving me mysql errors form several tables when browsing ste also saving values from backe end
Error displaying the error page: SQL=SHOW FULL COLUMNS FROM sltdb_template_styles: SQL=SHOW FULL COLUMNS FROM sltdb_template_styles
How to overcome this .. please advice ?
It looks like database connectivity
Try to access the database from the application server using the command line. or try to access your database via PHPAdmin
If still no chance:
Here is fix - i got for google
Use Extension manager->Discover and Install, possibly followed by an Extension manager->Database and Fix when needed.
Joomla requires a proper working infrastructure. Something must have failed otherwise the update should have succeeded. The above steps are normal procedure for fixing when something went wrong. An alterative would be to restore and try again.
Also, Joomla allows you to break down the steps. Using the Extension manager install from directory is the least resourceful way to update. It requires you to download, extract and copy it to the webserver yourself.
Hopefully this will help someone. I had this issue after a server move and it turned out that it was due to a module (wp_posts) that had old db credentials in it, i corrected the credentials which fixed the issue.
Unrelated but one other thing to check if you have this type of issue is can you update things in admin, I had a secondary issues with was that APC cache was not enabled on the new webserver, i discovered that by trying to update things in admin and viewing errors.
The error 0 message is very unhelpful, it seems this could be module specific though rather than joomla itself but it seems quite poor that a module can block the entire site form working, some error trapping needed me thinks!
Cannot comment, yet ... (as a comment to logicc's answer)
Well, the "Error: 0" is indeed not very helpful, but with debugging turned on, you at least get a good idea of where the problem might be coming from:
24 JDatabaseDriver->loadObjectList() /.../modules/mod_wpposts/helper.php:91
25 JDatabaseDriverMysql->connect() /.../libraries/joomla/database/driver.php:1312
About the module blocking the entire page - that might make sense in some cases (a module so important that you would rather have the page not render, at all, than in part?), but it certainly seems like a bad default. For now, I think modules should take care of that themselves with some try-catch-ing.
I have WordPress website running on a GoDaddy Linux host. The error PHP Fatal error: Cannot call overloaded function for non-object in wp-includes/class-wp.php on line 529 is being happening at random, usually in response to a POST request, I think.
WordPress version: 3.8
PHP version: 5.4.23
Line 529 of file wp-includes/class-wp.php is the body of the following function in class WP:
function init() {
wp_get_current_user();
}
The error seems to be somehow related to the presence of the WooCommerce plugin. I haven't seen the error when the plugin is deactivated.
Unfortunately, removing WooCommerce is not an option so I need to discover how is the error being triggered and provide a solution. The problem is I don't know what to look for.
I want to understand what causes an error like the one above in a general case.
Can anyone provide an example of PHP code that generates such an error? or
an explanation of why it happens?
I'm hoping to be able to use that information to find a similar problem in WooCommerce's source code.
I took a quick look at PHP's interpreter source code (here and here) and found the line that generates the error message, but to be honest, that didn't help me.
A question in SO about the same error in a different application has an answer indicating the problem was caused by server overload. I don't think that's the case here. We don't get too much traffic.
A different question in WordPress SE offers two possible causes. Either the problem is associated with Alternate PHP Cache (APC) being enabled or the problem is caused by a plugin. Unfortunately nobody offers actual solutions or specific causes.
My case is similar to the one exposed in the question above: I have APC enabled (currently trying to get help from GoDaddy to disable it) and my tests suggest WooCommerce has some responsibility.
I appreciate all your help.
Go to root directory and create a php.ini file and write the following
;extension=apc.so
and save.
Neighbourhood Wordpress theme had this issue.
I was able to solve this for individual sites by adding php_flag apc.cache_by_default Off to .htaccess
We found that this is related to the APC module for Apache. To resolve it, simply edit your php.ini to uncomment the apc module so it reads from
extension=apc.so
to
;extension=apc.so
This will resolve the problem.
I had the white screen of death for some time.
Prior to that a related issue -PHP Fatal error: Cannot call overloaded function for non-object in wp-includes/class-wp.php on line 529. This issue was solved by upgrading my godaddy account.
As mentioned above, the white screen issue could either be a plugin or the APC.
The fastest way to determine if it is a plugin is NOT to deactivate them all and then reactivate one-by-one - but rather deactivate and reactivate all at once - the plugin causing the problem with get an error reactivating.
That said, I wanted to keep the plugin so I contacted Godaddy, who readily disabled the APC.
I have reactivated the plugin and all seems fine.
The only potential issue with disabling the APC is slower load times, but I haven't experienced that yet.
I've brought this issue to the OS-Ticket community forum but haven't yet had a reply. I'm trying to install the latest version (1.7.0) and am getting the error:
Unknown or invalid schema signature (d959a00e55c75e0c903b9e37324fd25d .. 9e85d0c8f8532e3b0be38e99aba07aa1)
I've looked at the source code but am still unsure why this error is being generated. Does anyone know how I may be able to go about resolving this issue or what may be causing it? I've installed the system previously on my local machine without issue, the server i'm installing to is however Windows and so i'm wondering if there are any known things to be aware of when dealing with this system / MySQL on windows.
If I can't find a solution are there any recommended ticket support systems I could perhaps use instead?
Many thanks in advance.
Just change the second part of signatures in the file-
include\upgrader\streams\core.sig
Reference
There is a post in their forums for a workaround.
Post #5: http://osticket.com/forums/showthread.php?t=13703
I contacted the Dev Team about the workaround around a month ago and they advised against it, telling me they were working on fixing it; and to give them 2-3 weeks. Thus far, I have contacted them again with no response and have found no fix.
I have not heard of anyone using the fix reporting issues. Still, comes with a "Use at your own risk" disclaimer I would say.