After working on SBT for such long time to get the forum section working in my existing application now iam facing the weird error.I have connected to w3 connections and implemented the forum section in my existing application and able to add topics and comments in w3 connections using SBT.
It is going well from many days with forceDisableExpectedContinue in managed beans as false but suddenly it started giving one weird error and that is "Expectation Failed".
When goggled found that i should add the System.Net.ServicePointManager.Expect100Continue = false; in code but iam using javascript code to get the access to w3 connections.
I added forceDisableExpectedContinue in managed beans to true and checked, it is working fine.But initially it was true still i got this error.I doubt that is it the problem solved because of restart or any other issue.It is not consistent behavior to track the root cause.Need to deploy the same in production and not able to say application is working fine.
FYI my application will connect through the IHS server.Do i need to add anything in managed-beans.xml ?
Chat section for support is much appreciated and useful instead of Stackoverflow for immediate support.
Access this link for better understanding https://dst05lp3.lexington.ibm.com/SBTTest/discussionForum.html?forumUuid=0d2e2f15-c014-41a0-aba6-634d3c72d981&pageGuid=MBC
Change the forumid and pageguid(tagname) to the one you have forum access .
Thanks in advance.
When trying with the old code suddenly iam getting the same error then changed the forceDisableExpectedContinue in managed-beans.xml and it got resolved .Hoping it is resolved closing this question.If found again then my resolution is wrong.
Thanks paul for giving bit support.
Related
First thanks to anyone who can help with this it's greatly appreciated.
As you can see by the title this is a very weird occurrence. I do a lot of work with testcafe and can't really explain this.
The scenario is at my company we raise instances in AWS put our product on the instance then run the automation. These instances are automatically torn down in around 3 hours so I can't really post an instance example as it will tear down. When I try to go to the instance I get stuck with a spinner at the login page. I tried firefox, chrome, chromium, safari, incognito, tor, etc... They all get stuck at this spinner, in fact, this happens to everyone in the company.
For some reason when I run some tests via testcafe on my computer using chrome on this instance it gets past this spinner, logs in, then just resumes tests like nothing is wrong. I have tried using localhost as the host, different ports, skip js errors, and other flags. I am updated to the latest version of testcafe. My theory is that it has something to do with the proxy server that testcafe launches (just a guess). I tried online proxy servers and even made a local proxy server but still, none can get past this spinner.
I'm pretty sure more info would be needed to help out on this I'm just not sure what to add. If any tips or logs to add please let me know.
UPDATE:
I tried a few more online proxy site and found one that worked (performed in the same behavior as testcafe). I believe at this point i can prove that its related to the proxy server. Now with that proved, im assuming there is no way to get around this issue right (meaning have testcafe fail)?
I have opened with testcafe and they have reported its a bug: https://github.com/DevExpress/testcafe/issues/6055
I'm using Reactjs to create a browser based web application which interacts with MongoDB. Everything was working fine until I added webpack. Now, everything still seems to be working fine except when I try to run the application I get a blank screen.
I've went through my code and can't see what I've done wrong and after doing some online research I believe the issue could be caused by any number of things.
Are there any logs which could be used to help investigate this? Failing that, is there a recommended way to investigate this?
As #konekoya stated, the Browser developer tools can be used to identify issues. In my case it showed the error that was preventing my browser from loading properly, I was then able to troubleshoot and solve my issue off the back of it.
I was tinkering around with my preferences trying to get emmet working for jsx files and I ended up turning on plugin manager. Now my projects won’t load and I can’t turn the plugin manager off without being in a project. Here is a screenshot:
C9 Error Screenshot
I have no idea how to fix this and from what I’ve googled the only thing I’ve seen that was close was this thread where the solution was that he had a browser plugin that disabled referrers. From what I’ve googled on the subject Chrome doesn’t allow referrer disabling so I’m not sure if this is the fix or not, nor do I know how to do it in Chrome. If anyone could help me out that would be great.
Also in the screenshot I've included the console. Some errors popped up as well as a notification of this:
[OT] Ace session not ready for: /weatherApp/src/containers/search_bar.js - will setSession when ready!
which would be the open file in c9. Not really sure what this means either and I didn't see any solutions when I googled the issue. Any help on this issue would be appreciated as I don't have access to any of my projects in c9 which is what I mainly use for an editor.
Thanks,
I'm using Codepen modernizr.js over 1 years. Suddenly it started showing error 404. That means the file does not exist but I don't think Codepen like website stop like this stuff without any notification because lots of peoples are using it.
Javascript location was [http://codepen.io/assets/libs/modernizr.js][1]
Example: [http://codepen.io/adobe/pen/FgIBC][2]
If that script will not work anymore then anyone has the idea to get back that Modernizr.js?
Thank you!
I send an email to Codepen.oi about this issue and they replied:
Hi Chinmay,
Thanks for writing in! The CodePen-hosted link to Modernizr is no longer supported. You can still get Modernizr for your Pens, though :) Start typing "Modernizr" in one of the External JavaScript fields and you can select it from the typeahead menu.
If you need Modernizr for your own website, you can get a hosted link at: https://cdnjs.com/libraries/modernizr
Thanks for using CodePen!
I have been having this issue for quite some time now and have been trying to find the problem but have come to no solution. I am hoping you can give me some insight as to fix this problem.
My live site is working on 1.8.1.0 with a custom theme from Emthemes (latest version). PHP Version 5.4.28. I have development sites running 1.9.0.1 right now and the issue was not fixed in the recent release. I also have my development sites running PHP Version 5.5.12 with no issues (for people looking at upgrading to latest PHP).
First, I contacted my Custom Theme provider and they stated the issue was with Magento base files since the "Your Checkout Progress" Panel does not work with Base theme either. Has anyone else experienced this?
Next, I have looked at every Forum post related to this issue and no solution worked for me.
I have researched other sites operating on Magento platform and the "Your Checkout Progress" Panel is working perfectly.
I am under the assumption from reading forums that the issue is either caused by opcheckout.js, checkout.xml or onepage.phtml but I have applied all of the fixes I found and nothing seems to cure this issue. I have also tried reverting to the base files but still nothing.
If you visit my website and add a product to cart then Proceed to Checkout you will notice the "Your Checkout Progress" does not update as you walk through the steps for Checkout.
My website is www.trucatchtraps.com
Any help with fixing the "Your Checkout Progress" will be greatly appreciated.
Thanks,
#user3383912 - Thank you for pointing me in the right direction.
I did not plan on trying this because when I talked to emthemes they said the issue was happening on the base theme as well. But when I disabled my theme, I noticed the "Your Checkout Progress" was actually working like it should.
After doing a little debugging, I noticed one of my extensions was overriding:
checkout/onepage/billing.phtml and shipping.phtml
So I hide these two files and brought the base billing.phtml and shipping.phtml just to make sure it would work, and voila everything was working like it should.
Then I noticed billing.phtml and shipping.phtml were extremely outdated (2009) so I updated with the new info from Magento 1.9.0.1 base files.
So I compared the two versions of the files and updated accordingly, I was still having issues. But what I did not realize is I have another extension working inside billing.phtml which was causing the issue in the first place. When I removed the 'Newsletter Opt-in' extension from billing.phtml everything was working again! So I have now moved the Newsletter Opt-in extension code to agreements.phtml and no problems.
FYI: Once I removed the Newsletter Opt-In code from my original outdated billing.phtml file, everything worked. So updating the file with the latest info from Magento 1.9.0.1 was not the solution but still needed to be done anyways.
This entire problem came from an extension that I did not even want to place on the website, but was told to do so...