Paypal PHP SDK Not found! Fatal error: Class 'string' not found - php

I need to execute the phpsdk paypal samples on:
http://www.fastbreakplay.com/preview/paypal/sample/
but I get the following error:
Fatal error: Class 'string' not found in
/home/fastbre/public_html/preview/paypal/sample/vendor/paypal/rest-api-sdk-php/lib/PayPal/Common/Model.php
on line 53

The product you are using is rest-api-sdk-php
https://github.com/paypal/rest-api-sdk-php
If you look under issues, two days ago there
was an issue reported that may be related to
your problem.
https://github.com/paypal/rest-api-sdk-php/issues/4
As you can see in the issue, they had some
issues updating. That could have messed up
all kinds of things. They were suggesting
removing the vendor folder and
composer.lock files; then doing a composer update.
Since your problem was in the vendor directory, and
you may have been installing around the time of
this update issue, you may want to try their
suggestion.

Related

Magento Fatal error: Cannot declare trait Magento\Framework\Interception\Interceptor

I got error after scanning the website with cpanel scanner.
Fatal error: Cannot declare trait Magento\Framework\Interception\Interceptor, because the name is already in use in /home/..../public_html/generated/code/Magento/Framework/App/State/Interceptor.php on line 19.
I have tried all answers related to this but no luck. I have update code from fresh Interceptor file as well but still same error.
Please help me to reolve this.
Link is https://www.advcylinderheads.com/
Many Thanks

Fatal error: Class 'Extendware_EWCore_Model_Autoload' not found

I'm getting the below error while loading my Magento(Version 1.7) in local.I have checked the google and tried few things like setting permissions(chmod),Flushing cache etc, But it didn't workout well.
Below is the error
Fatal error: Class 'Extendware_EWCore_Model_Autoload' not found in /Applications/XAMPP/xamppfiles/htdocs/magento/magento/app/code/local/Varien/Autoload.php on line 14
Can anyone suggest me what to do on this?
Thanks in advance!
Can you please check for the configuration file in the directory:
app/etc/modules/
Look out for a file which has registered probably Extendware_*.xml there might be more than one of them which will need to be disabled/removed.
Please clear cache to update the configuration.

Fatal error: Class 'CI_Controller' not found in H:\php2\htdocs\property\system\core\CodeIgniter.php on line 233

In codeigniter i have started one property related project for my client.
I am getting an error
Fatal error: Class 'CI_Controller' not found in H:\php2\htdocs\property\system\core\CodeIgniter.php on line 233 after i have complete some development.
I have really search it for many time in google and in stackoverflow but still didn't get solved.
Thanks in advance,
Well, m not sure but i guess it can happen because of changes in database settings.
codeigniter sometimes show this very weird behaviour that giving this fatal error "CI_Controller" not found even there's nothing wrong with the core files.
so- try debugging like this-
1)check your database seetings located at config/database.php
2)If it does'nt works, re-uploading the system files.
I hope this helps.
Check your database config in application/config/database.php it's one of the major time consuming error message I faced with CI. Because the error message was simply misleading. So, check the database config first.

Drupal failed after update

I just updated Drupal core from 7.4 to 7.26. After running update.php site stopped working – both public and admin part. When I load it fatal error occurs:
Fatal error: Call to undefined function _system_default_theme_features() in /[drupal_path]/includes/theme.inc on line 1422
and when I reload it another fatal error apperars:
Fatal error: Call to a member function getDirectoryPath() on a non-object in /[drupal_path]/modules/image/image.module on line 83
next reload – first error, one more – second. Also, second error is loading much faster.
And one more thing, after applaying update.php I got one failed, I don't know if this is connected:
media_gallery module
Update #7009
Failed: FieldException: Próba aktualizacji egzemplarza nieistniejącego pola media_gallery_media. w field_update_instance() (linia 557 z /[drupal_path]/modules/field/field.crud.inc).
which is something like:
Failed: FieldException: Attempt to update an instance of a nonexistent field media_gallery_media. in field_update_instance() (line 557 in /[drupal_path]/modules/field/field.crud.inc).
PHP Version 5.5.6
Any tips where the problem is? I was trying disabling some modules from db, but this did't help.
It's difficult to explain the reason and to provide a solution.
My attempt would be to copy the DB and the files on a neutral platform (local machine or so) and experiment with the update.php script.
My suspicion would be that media module needs also update since it's using the old URI function definition (call). Also try to update other modules that are working with files.
The update is quite big since 7.4 to 7.22 (years of improvement). Reading the change log would be helpful but not realistic.
Did you also cleared the cache? (via drush if the web interface not working - /?q=admin/config/development/performance)
Please don't forget to post the solution if you find one for other users with the same issue.

I get a fatal error after attempting to install wp-ecommerce plugin, can not find any other support with same error

I attempted to install a wp-ecommerce plugin, it gave me this fatal error and now it only shows the fatal error message when I try to access my wp-admin.
Fatal error: Cannot redeclare class wpsc_gateways in /home4/stickdog/public_html/wp-content/plugins/wp-e-commerce/wpsc-components/merchant-core-v2/classes/wpsc-gateways.php on line 6
If I can access my file manager and I just delete the plugin will it solve my problem? I would rather use the plugin but if it won't work its ok. Thanks for your help.
From a programming perspective it seems like the PHP class wpsc_gateways is being redeclared in the coding. But since this is a pre-packaged plug-in that seems odd. Perhaps sloppy coding on the part of the original author. If you delete the plugin the problem will be solved. But maybe the plug-in was installed twice by accident? Look at the contents if your /home4/stickdog/public_html/wp-content/plugins/ to see if that might have happened.

Categories