sencha touch 2 api docs - sencha-touch-2

I'm currently working on a project with Sencha Touch 2 and was wondering if anyone has a working link of the API docs page.
I've tried accessing http://docs.sencha.com/touch/2-0/#!/api, but I'm constantly getting redirected to: https://www.sencha.com/products/touch/2-0/#!/api and am finally given a 'The page you’re trying to reach could not be found.' error from Sencha Touch's homepage.
Does anyone have any idea why this is happening? I'm seeing the same link given on all my searches and hence I'm starting to get the feeling that this isn't just a faulty link problem, but perhaps something else.
--update--
The missing page error is occurring on Chrome. IE seems to be handling the link OK.

I don't know why you got that strange problem because the link is still Ok for me, maybe you need to clear your browser cache or something else.
But instead of that way, if you've already download and unzip the sencha touch 2 package from here and I think you've already did it, so you just need to open the index.html file in that folder, the API docs are already there :)

I've fixed the error by disabling the KB SSL Enforcer extension in Chrome.
Hope this info. helps others facing the same problem.
The inability to read the docs in chrome was driving me mad for a while.

You have downloaded the sdk right??? just go to your sdk folder and go to docs in your web browser the docs is right there...

Related

Error deploying vue app using any type of deployment

I have only deployed a couple small apps before and I am still newer to deploying apps in general.
I created this app by following a course and have recently finished the project. The course did not provide instructions on how to deploy the app. I have used Firebase hosting a couple times and am also somewhat familiar with Heroku. Regardless, it all seems pretty straight forward after following documentation.
I first tried Firebase hosting since that is what I am most familiar with. Spent some time with that with no luck, then tried heroku, then netlify, then NOW. Every single one of them had issues without any real information on them.
NOW says deployement failed with no logs.
Firebase hosting doesn't seem to be logging any errors, it builds a blank page.
Netlify says page not found after deployment and Heroku was something similar.
I am 100% open to getting this simple app deployed using any approach at all (preferably the easiest one).
Since I am following documentation and there doesn't seem to be any errors being logged, I'm completely stumped and am not sure what to do.
I realize I might not be providing the most helpful information to solve this issue, although I do have my full repo here:
https://github.com/SIeep/austin-pizza
Would anyone be kind enough to look over my repo and see what the issue might be? Or even point me in the right direction?
Please let me know if I need to provide any additional information.
Thanks!
missing entry file or file path problem ?
Try to find out which stage the problem is at first.
Compare this and last successful Firebase Configuration(dependency path),
Compare this and the last build dist file (not detail code,just File structure)
compare webpack.config.js
(app can run well locally,so i think it wouldn't because of the problem with the app's own code)

Google Colab running any cell received javascript related errors

Received a browser white popup saying when executing any cells:
Error
Could not load the JavaScript files needed to display output.
This is probably because your Google account login access has expired or because third-party cookies are not allowed by your browser.
Please reload this page.
DETAILS
I have tried re-login and restarted runtime, and no help. Strange is another notebook is fine.
OK
Update: Just restarting browser and relaunched everything seemed to "fix" this.
For those like me who tried all the given solutions but with no use ,the magic thing that worked for me in the end was to open colab using a vpn!
Restart browser. If someone find a better way, please post.
I got this error on chrome. Every colab notebook I opened had this issue even if it wasn't connected to a runtime.
Restarting the browser didn't help.
Clearing cookies of last 24hours (and restarting my system to be sure!) fixed the issue.
This may be because access to your Google account has expired or because your browser does not allow third-party cookies.
Check your task manager on your laptop and see how full the disk is.
Mine was 100% so I searched “disk cleanup” on my Windows computer And got rid of temporary files and files downloaded from internet, etc. also clear cache and cookies on whatever browser you’re doing. And if you have synced your google chrome and Microsoft edge specifications as the same(cookies, extensions, etc) then get rid of both cache and other stuff on them as well. Also check 3rd party cookies
Using vpn solved this problem for me
The library I'm using by default prints a large amount of info, which caused this problem for me. Restart the browser only works if it doesn't print that much again. Disabling the verbose info printing solved the problem for me.
I found when the notebook is heavy it is throwing up this error. For example there were so many plots in my notebook, that slowed it down and caused this problem. Also make sure you don't have multiple notebooks opened.
Try Cleaning your trash/recycle-bin & temp files.
That worked out for me.
Disabling some AdBlock extensions works for me.

How to Handle URL Link Tap Events using PSPDFKit for Titanium

I am using the PSPDFKit Module (v2.8) for Titanium Mobile (3.0.2GA) to both display cloud based and local PDF files within my App. The module works a treat (great job by the developer), however I've run into a problem.
Some of the PDF files have links to external websites within them, and when they are tapped I am getting a No system handler registered warning. I've checked the documentation and forums / google and cannot seem to located how these events should be handled.
Does anyone have any idea – any help would be appreciated!
Now external links are supported, so this might be a bug. In older releases there was an issue where URLs like "Http" or "hTTp" (note the uppercase) weren't properly detected. That's all fixed in the later releases (2.12 and up). Please update and let me know if this is fixed or if you're still seeing problems. Thanks!

Safari can't get HEROKU's cookie

I am sorry that I am not able to provide much info because I totally have no idea about this weird problem.
I have a fb canvas app which is written by rails 3.2.2 .
There is not any problem on my local machine (Mac OS X 10.7.4).
When I deploy it to heroku, it is fine with chrome and firefox. However, when I use Safari to browse it, Safari can't get any cookie from heroku. (it shows "This site has no cookies" in developer tool, but it works well on my local machine.)
I have googled this problem, and I get something like this and this, but I don't think these are the case of mine.
any suggestion?
If you need any specific info about my code to solve this problem, please let me know.
I will appreciate it very very much!!
I finally found out that it's a problem of safari's security setting.
As fb canvas gets heroku's content through iframe, there may be security issues. If we donwgrade the 'Block cookies' of safari's privacy settings from 'From third parties and advertisers'(default) to 'Never', everything works well!
However, I don't think asking users to downgrade their security settings is a good idea. I am wondering whether there is a solution to avoid this restriction in safari.
please let me know if you have any idea. many thanks :)

Safari blank page from Umbraco-driven site

I am running a site using Umbraco 4.
In Safari (Mac) when I refresh the page I get a completely blank page; the page appears to have finished trying to load.
I'm using a lot of JavaScript so I tried to removing all JavaScript but the error still persists.
The site is here
http://www.dreamguts.com/
I would really appreciate any input.
I have done some digging on this and it would appear to be a bug in Webkit:
https://bugs.webkit.org/show_bug.cgi?id=26621
The bug report suggests that disabling the WebCore cache via Debug menu may help.
Tim