Locally everything is working. But when I create a container and push it to cloud parts of website don't get localized. So far have no idea why as there are no errors thrown.
What is the best way to figure this out?
I checked the po files and they look OK.
Related
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.
I have an app developed with CakePHP and it is working just fine on my local machine. Now, I wanted to develop another app with CakePHP. I installed cake in a different folder, configured vhost and server block and did everything like for the first app. I created an empty app, just basic controller and view and when I type the address for the second app I get the first app!!! Weird thing is that all links are working and when I click I get in browser url like secondapp/companies but the content is firstapp/companies. Once more, the second app is empty, no controllers, views and models, just a basic one. Then I did all that in htdocs, and the same problem occurs (none of the apps wasn't in htdocs, but in folders on E partition).
Can someone please give me some help before I kill myself?
Thank you...
If the problem is not on the database configuration, maybe cache problems ? Try it on a private browser/incognito ?
Some advice would be appreciated.
I am trying to install the Google drive Realtime playground onto the online Google App Engine. (as well as trying to get it working on my Localhost.
Once uploaded, it renders but all functionality is greyed out. Link to example: https://alpha-113.appspot.com
I have added the client id and app id as stated (within the readme) into the correct .js file and updated the app.yaml file to include the application name.
I am stumped.. Can anyone assist?
James
If you view the output in the Javascript console, you see that you have a number of errors in your javascript. It looks like the underlying problem is that your CLIENT_ID has invalid syntax. It should just be the number. You can't have "."'s in a value in javascript like that.
A number of years ago I wrote a .aspx page that handled a HTTP POST Request which contained a piece of xml. The code read the xml using Request.InputStream - it worked fine for years until The DNN site that it was running in was updated to 5.6.8 now Request.InputStream is always empty. Note that the page is completely separate to DNN but located in site.com/Special/tlweb.aspx .
I've tested the same page on the same server using .net 4 but with a different IIS site and it works fine. Since another app POSTS data to the current URL I need to get it working in the existing location - changing the app is not an option.
I kind of think something was done in DNN 5.6.8 that was intended to stop cross site scripting attacks but I'm really having trouble figuring out what changed and what I can do to ensure that the specific page runs as it did previously.
Can anyone make any suggestions please?
Thanks
Josh
I am using C1 3 and am having problems with the preview pane.
The C1 site uses master pages for templates, and works correctly when published. However, it is not displaying correctly in the preview pane. It visually appears to be ignoring CSS settings.
This site was copied from an original install, on another sever, that works correctly.
Any tips and or ideas would be greatly appreciated.
*UPDATE**
In the content view, which is not working, it is using this url
http://www.abc.com/Composite/content/Frontend/Images/logo.gif
All other sites, including the published version of the site above use this url
http://cms.abc.dev/Frontend/Images/logo.gif
I am assuming the same is happening for all images and style sheet references.
However, I cannot find where this is happening. In the master page items are referenced as follows:
href="~/Frontend/Styles/layout.css"
ImageUrl="~/Frontend/Images/logo.gif"
Thats weird... have you somehow accidently configured the /Composite/Content folder as an application? Thats almost the only explanation why asp.net would expand ~ to /Composite/content/ instead of just /.
The preview-tab is handled through a wrapper-page that lives inside /Composite/content, unlike normal viewing of published pages which is handles by the root itself.
I think i found the problem...
I created a new app pool, used it, and now it works.
I guess the app pool somehow got corrupted...