noob: Not able to checkout code using Bazaar explorer - dvcs

So i started Bazaar explorer and set my local path to a project folder on desktop. I have an http URL in the format http://XXX.XXX.X.XX/trunk..I tried checking out the code by entering the URL in the Branch Source but I get an error saying "Connection error: while sending OPTIONS /trunk/: attempt failed as cannot connected party failed to respond or host failed to respond. Please help!

You're trying to checkout SVN repository most likely. Something wrong with access to that repository or with bzr-svn plugin. You have to file a bug here and ask your question, and you will have more chanches to get the right answer there than on StackOverflow..

Related

Error on deploying website to IIS - App still refers to local files directory even after publish

Has anyone experienced this issue before? I published a website using File Deploy and placed it in an IIS. Other apps works just fine, but the website I deployed shows this error:
It seems to still be pointing to my local directory. I've updated the paths but to no avail. Help please.
Thanks in advance.
The paths show locations at compile-time, that is not a problem. Here, you are getting an exception on line 65 in DataAccess.cs - object reference not set to an instance of an object.
If you set custom error "on" (in the web.config), you can get more info about the exception. In the "Network" tab of "Developer tools", you can check your request and response.

Warning: error_log: failed to open stream: Permission denied

I've been working in Silverstripe 2.4.10. I'm still learning a lot about this content management system. I've been working on an update for the website and since I've put the update online I keep getting the error message in the admin panel of the CMS:
Warning: error_log(../mysite/logs/warning_log.txt) [function.error-log]:
failed to open stream: Permission denied in /home/www.mysite.com/web/sapphire/dev/LogFileWriter.php on line 57
I have already tried to restore the website to the original code, since I've backed up the old code, but the problem still occurs. I've been looking all over the internet and can't find the answer.
In silverstripe 2.4 the logging directory was setup with...
SS_Log::add_writer(new SS_LogFileWriter('/my/logfile/path'), SS_Log::ERR);
I can only guess that somehow that has been given the inappropriate path of mysite.
Searching for "SS_Log::add_writer" call or other log methods (see docs for 2.4) should help you find the code to fix it.

Response for preflight has invalid HTTP status code 401 preflight OPTION call error

I'm working with Ionic 3 framework project and have encountered one error whenever i m trying to send my data to the server by POST method (as postAsync), this is related to the OPTION call as the error says:
Response for preflight has invalid HTTP status code 401
I don't know how to solve this error, as I have added CORS extension to my browser, still I'm facing this error issue.
Is there any solution to solve this issue from browser side like from chrome devtools as i can filter it from network by -mode:OPTIONS but at console I'm having the same error.
If this not possible, then how to solve this error ?
Code:
this.WooCommerce.postAsync('customers', customerData).then( (data) => {...}
More error messages:
polyfills.js:3 OPTIONS tusharstar.freesite.host/wc-api/v3/…... 401
(Unauthorized) (anonymous) # polyfills.js:3 ... (index):1 Failed to
load tusharstar.freesite.host/wc-api/v3/…) Response for preflight has
invalid HTTP status code 401 bluebird.js:1545 Unhandled rejection
TypeError: Failed to fetch
After googling a lot and i really mean a lot, the answer to my 1st point is yes! It is all about the web security issue/precaution which lets the developer get the error/precaution point of OPTION call with chrome browser. Simple way to solve the problem (just for development purpose) is to disable web security for browser, restart chrome with new extension of disabled web security .exe and everything will work fine. Steps for windows user:
1.Close chrome.
2.Open cmd
3.add this code:
C:/Program File/Google/Chrome/Application>chrome.exe --disable-web-security --user-data-dir="D:\chrome"
You can get through this very easy! Let's follow me right now
Create a shortcut on your desktop
Right-click on the shortcut and click Properties
Edit the Target property
Set it to "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --5. disable-web-security --user-data-dir="C:/ChromeDevSession"
In VIsual Studio Code, run ionic serve -l
You're gonna see new tab open http://localhost:8100/ionic-lab. You should be aware that this link is opened in the normal chrome tab, not the "disable-web-security" chrome we have set up.
Double click to the shortcut that we have set up to open the "disable-web-security" chrome tab. Then paste http://localhost:8100/ionic-lab into this tab.
So the reason that we get multiple errors when working with woo-commerce-api is this "web-security" by Google. Then you just disable it and you actually don't need any CORS Extensions. So remove them right now if you have installed.
And this solution i write for people who learn this course https://www.udemy.com/ionic-3-apps-for-woocommerce-build-an-ecommerce-mobile-app/. This is an ionic e-commerce app that using woo-commerce-api to set and get data from Wordpress (local or live server). If you have trouble in other language not ionic, it still works fine.
Actually i have done a lot of searchings on Google to find this solution. I hope this helps all of you. Now, i need to go to bed because tomorrow i have a final report about this ionic project with my lecturer 😃
See ya!
Quy Le
I had the same problem and I solved it by adding some lines of code in the top of .htaccess file of my WordPress root path (C:\xampp\htdocs\wordpress)
Add this code in the top of your .htaccess file :
RewriteEngine On
RewriteCond %{REQUEST_METHOD} OPTIONS
RewriteRule ^(.*)$ $l [R=200,L]

Enable GitLab to display error

I have installed an omnibus GitLab package on my linux machine, and i try to configure it. Everytime i have a page "ERROR 500, Whoops, something went wrong on our end.". I don't have root access and looking at the log files is very compelling for my team and me.
Do you know if it's possible to definitively enable displaying errors directly in web page ?
I looked for a configuration variable in the /etc/gitlab/gitlab.rb file, but nothing found.

MVC4/IIS7 Error 500 diagnostics. No stack trace, no event log

I have an MVC4 project which worked fine on the (IIS7) server. Then I moved to a new laptop, so of course all the NuGet packages I'd installed had to be uninstalled and reinstalled with different versions in order to get it to build (all I'm using is dotless and whatever dependencies it has, but that appears to be more than nuget was ever designed to cope with).
It now works fine again on my new laptop, but on the server all it does is give me an Error 500. No stack trace. There's nothing in the event log on the server. I set up Failed Request Tracing but the log file directory is empty.
I created a file on the server called test.html:
<p>test</p>
That can't be served either. Error 500 again. Nothing in the failed request log directory, nothing in the event log.
Everything else on that site on that server works fine.
So my question is: Is there any known way to set about diagnosing a situation like this?
UPDATE
It turns out I misconfigured Failed Request Tracing, and had it only enabled for *.aspx. When it's enabled for *, I do get fr00000?.xml in inetpub\logs\FailedReqLogFiles\W3SVC1, one for each failed request.
The problem turns out to have been something broken in web.config
Sounds like some configuration issue with the site and how it's set up in IIS. Without being at your computer, it's hard to say with any certainty, but my best guess based on experience is that you've got a permissions issue with the directory that's being used as the docroot of the site. Make sure IIS_IUSERS has at least read and execute access to that directory.
It turns out I misconfigured Failed Request Tracing, and had it only enabled for *.aspx. Once I had it enabled for *, then for each failed request a sequentially numbered log file was created:
inetpub\logs\FailedReqLogFiles\W3SVC1\fr00000?.xml
...etc. Those files contain a staggering amount of detail.
I searched for "exception" in that xml, and the problem turned out to have been something broken in web.config
So this was pure stupidity on my part.

Resources