When trying to install PayPal, the following message appears (screenshot attached). Please help quickly. Thank you very much in advance.
I would like to add that I am able to install and configure other modules normally.
When trying to update the modules, including the PayPal module, there was some error. I decided to re-install the PayPal module but encountered a problem that the files could only be up to 2M. I eventually fixed this by changing the limits in the php.ini file. After that, I was able to upload all the modules except for PayPal. PayPal was giving empty errors. I tried some things and finally, it started giving the error that is on the screenshot.And also worth mentioning that for a moment I replaced the paypal folder in modules with the one I downloaded in the zip file of the paypal module but I reverted that change.
Related
I've been getting this error while trying to create a script file to automate a little of the codePush deployment process.
Looking at all the information I could find online wasn't helping - In the script I echo'd the PWD to see that I am running the code-push release-react command from the correct location in my .sh file, I am including react-native as a package dependency in my package.json. Everything looked fine, but I was still getting the error.
Since I found the issue but couldn't find anything online to point to what the problem was, I'll post the answer below.
Upon playing with the scripts in my package.json I tried running npm install again to make sure everything was setup properly when I get an error that actually showed me my issue.
The problem was the JSON in my package.json had become corrupted - the syntax wasn't spot on. I had started playing with the json in the file and forgot to revert the changes I made when I finished and had an extra comma.
Now that almost a whole day is gone, I can get back to work.
I am installing modules in CMSMSbut they are greyed out and I can't use them. Tried uninstalling, re-installing to no avail. Thought it was just form builder at first, but then tried the slider, gallery, all the same.
I'm using CMSMS 2.1.3, php 5.5.34, apache mysql 5.5.48.
Don't know what's going on.
thanks, Matt
Check Site Admin > System Information for any identified errors or warnings.
If that doesn't help in the top right of that Admin page click the 'View Text Report' and provide those details here. Will help others give you some more specific advise.
Another thought ... try reinstalling the core in case there was an issue with the files or installation.
I have installed Laravel and and I am playing around with it.
I am following the tutorial :-
http://geekanddummy.com/how-to-laravel-4-tutorial-part-3-using-external-libraries/
I need a new library and have added that in composer.json.
But when I run
php composer.phar update
I get the following message :-
Composer could not find a composer.json file in
What do I need to do to get this corrected..?
I'm the author of the tutorial you link to (hope our Laravel tutorial series is of some use, by the way). I can't quite tell from your answer whether you restored all the content of the original composer.json file when you created a new file of the same name...? You definitely shouldn't need to nuke the composer.json file and start again. As you probably know, that file contains all the Composer-based dependencies for your Laravel project, so you would of course lose significant functionality if you were to wipe it and leave anything out when you start again.
The error message looks to me like you're either in the wrong directory or it's a permissions problem with the composer.json file. It's too late to be certain now, but if you come across the problem again, try running:
chmod a+r composer.json
at the console/ssh shell before running composer update. This restores read permissions (for all users). You may also wish to check file ownership. (Both commands assume we're in a Unix/Linux system, so YMMV.)
Watch out also for instances where you're running a Composer command with the global parameter. This will cause an change that relates to wherever you've installed Composer, rather than the directory you're currently working in.
Note that you can also update using the --working-dir parameter, thus:
php composer.phar --working-dir=/path/to/laravel/project update
Hope this helps.
Rob
Deleting the existing composer.json after copying the content and then saving a new file with the same name works.
If your on windows (at least in my experience) you actually use just 'composer', not composer.phar/.json or any extension.
composer update
composer dump-autoload
This is all I need to type in to be able to access composer in my laravel directory.
i had the same issue, tried several many solutions that worked for others but not in my case.
then some-one told me to drop the 'php' and '.phar' from my command. i.e. directly use
composer update
composer create-project etc.etc.
and to my surprise it worked..
Occasionally, and for reasons that remain a bit vague, restarting the server seems to solve the issue. That step might be worth trying before making changes to file permissions.
Go to https://git-scm.com/download/win
Then download related version and run your composer command inside the git bash
Or else you can use vscode bash;
enter image description here
I was trying to submit my second app update and it failed submission after passing validation. This is the error:
"Unable to create configuration directory:/Application/Xcode.app/Contents/iTMSTransportation.woa/.itmstransporter. Cannot save local copy of remote diagnostic configuration;local path is not writable".
My screen shot of the error cannot be attached. I know it is not a network error at Apple's end because it specified a path in the Application Loader in Xcode. Since the system has read and write permissions here, it cannot be because I changed something. I submitted another app successfully earlier on the same day without a problem (as usual). I am at my wits’ end. Anyone experienced this?
Since there is no “Build for Archiving” in Xcode 5 (like in Xcode), I started with following steps:
1 - From the Xcode Product menu I selected “Archive” item
2 - After the Build, the organizer window appeared in the foreground with my archive in it.
3 - I clicked the “Validate…” button and it executed that successfully.
4 - When I clicked the “Distribute…” button, it started uploading the app but failed and came back with the aforementioned error. I went to the folder to see if any folder in the directory path is locked and also to see who has read and write permissions. It is not me but the system. I did a Disk Permission Repair in Disk Utility but that didn't help.
I then removed the offending file “.itmstransporter.” and tried to submit but got a different error. I put it back and took out the other two (ITMSTransporter.cmd and WOBootstrap.jar” but produced a different error. So I restored the folder to its original contents and returned to where I started - stymied. I have considered installing a new version of Xcode 5.0 but I don't know if that will help.
My OS:Mountain Lion 10.8.5, Xcode 5.0, MacBook Retina (first retina in 2012). Project compiled for iOS 7 in the Build Settings.
Thanks for any pointers.

I had the same issue. I copied the whole "Application Loader" out of the XCode package to somewhere else and after that, uploading from the Application Loader worked fine.
I get the following errors whenever I start a new project in eclipse.
One thing to observe is the strange path at the last, which i dont know why, comes always in the error message.
ps: the greyed out area is my username.
It looks like you are running Windows 7. Check the security settings on the folders you are working with and make sure that your user has the appropriate permissions on them.