2sxc TimelineJS thumbnails failing? PagePeeker.com API issues? - dotnetnuke

I have a new deploy of the latest version of TimelineJS app running on 2sxc 9.42 and for reasons I can't seem to figure out or find any useful errors on this, the api.pagepeeker.com seems to be failing or not getting used. You can see at the link below that it has worked sometimes, but as you progress to the later entities, it just gives up and displays the URL for the media without trying to create a thumbnail.
https://www.glencoeparkdistrict.com/News/Special-Projects/Timeline
I have tried restarting the app pool, clearing the cache and deleting and re-adding the items, but am unable to get things working as expected. Is there some way to force the API to retry getting the initial thumbnail?
How can I debug this or get a handle on what is going wrong here?

Related

React app get stuck on reload on Firefox desktop, but not on Chrome and other browsers

I have a create-react-app build being served by flask. It works fine in other browsers; however on Firefox, when I do a reload, the main.js file is stuck at the fetch method. After 3 minutes, it timesout then renders what it suppose to. I am looking for guidance on where to look from hereon. The production server does not log that the endpoint is receiving the fetch request; however, once the 3 minutes is up, the client side renders the updated information (as if it hit the server side). Everything looks like it should be working in the code I wrote, but I am not able scope out where I should be looking in debugging this issue.
Note: I am giving a broad description of the problem at the moment, but will disclose specifics such as codes, logs, and others items once I am able to get some guidance of the matter. As of now, there are no resources pointing out this specific issue, thus displaying code will simply be a "garbage" dump.
After working on the problem for quite some time, we found these two articles to be very helpful:
https://www.andreasreiterer.at/fix-whitescreen-static-react-app/
https://blog.miguelgrinberg.com/post/how-to-deploy-a-react--flask-project
After testing different sources, we first found that article one's suggestion of changing the homepage to the base url worked. After realizing that the nginx was getting confused on which static files to server, we proceeded to follow article 2's steps.
We did not have any issues on other browsers, but only on firefox. I hope this will help those that are experiencing the same Firefox issue.

Showing failed re-building development npm/react/gatsy errors in browser

I'm doing development work using gatsby develop. Basically, this script monitors the source code files and re-builds whenever there are changes.
When the re-build succeeds, the browser automatically refreshes and shows the newly built page.
However, when the re-build fails, the browser does nothing, and if I were to manually refresh the webpage, it still loads the last working version, leading to confusion as to why my changes are not reflected.
The only way to tell that the re-build failed is by looking at the terminal output of gatsby develop, which I often hide in order to maximize screen real estate.
Is there a way to for me to just look at the browser and code, and be able to tell that a re-build has failed? The best would be to have the errors show up in the browser, much like the javascript errors, where the re-build was successful, but the code ran into issues in the browser, i.e. TypeErrors, undefined etc.
Thank you.
After #gnujoow's comments, I did a quick check and realized that build failures already show up in the browser.
For some reason, my browser does not always refresh when there are build failures. Thanks #gnujoow

Ionic error: Unfortunately app has stopped

I know this is a repeated question, but still I am posting the question as I unable to find the answer by all the method i check in the previous links. So, please help me instead of marking duplicate or voting down.
I have build an app with some cordova plugin including the push notification, but in some handsets its working good and in some its showing me as "Unfortunately appname has stopped" and the app is exits.
I have tried with some options like updating google play services, sdk update, adb logcat, keyboard uninstall and install, even platform also i have added again but no use.
Please save me from the bug.
Ultimately I have found the solution.
The error was the cordova-android#7.0.0 version.
I just updated my package from 7.0.0 to 7.1.0 and just re-installed all the plugins and its working pretty fine.
Now all the plugins even the push notifications are working good.
If anyone has the issue can just follow the same procedure and it will help you.

Protractor tests on BrowserStack iPhone devices are not working

For some reason the iPhone devices are never able to load the url requested by Protractor, they always show a blank page. It tries to load the url several times and then gives up.
The other BrowerStack devices all seem to work, including Windows, Android, and Safari/Macbook.
Has anyone encountered a similar problem?
For reference, we're using Protractor v2.2.0 (have not been able to updated because we're stuck in an old version of NodeJS, but we could try if that is the cause of the issue).

App Engine doesn't recognize file change

Often times when i make small changes in my python or html file and upload it to Google App Engine, the changes doesn't seem to apply. I tried clearing my browser cache, and refresh, but still can't see the small change i made in my html file. How do i fix this? how do i know that the changes get uploaded?
Major changes seems to get updated just fine. But if i change a character for example, it doesn't get uploaded. I can't seem to see the change after clearing my browser cache. So, i assume it doesn't get uploaded. Anyone has experience with this?
Does the version in app.yaml match the version that's selected as default in the admin console? A mismatch would explain what you're seeing.
I had the same problem in Java with eclipse. I had to clear all my project and close eclipse, reopen it and deploy my app to appEngine..
Hope it help you

Resources