i am a new yii developer. I got ready working project from my friend(yii1). But, when i run it in my localhost nothing is happening except white page. I do not know why. Please, give me hint to about the causes of this case.
Do you have error reporting enabled? See White screen of death for more information.
If your friend can run it without problem, it might be because database connection is not set properly. See in /protected/config/main.php, under components. There should be either connection to database or link to the file, where the connection to database is set.
Related
Attachment
I'm currently working on a website.
Attached is the part of the website that I can watch on my computer monitor.
Changed Display below is the what I want.
However, if I keep hitting 'ctrl+f5', the screen shows me either unchanged display or changed display.
I have no idea why it shows me two different types of screen.
As far as I know, 'ctrl+f5' deletes the cache and updates data but it is not for me.
Ridiculously, If I keep hitting 'f5', I can only have the changed display as I want.
I guess I have a problem on css because I get an error message: DevTools failed to load SourceMap: Could not load content for http://localhost:8090/asset/css/sub.css.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE.
Does anyone know the keys on this problem?
There's not enough info here for anyone to tell you how to fix your problem with any amount of certainty.
What do you mean by changed display? Just the website looking different? Or a different debug preview (like scaling your website down to a phone's screen size)?
If it looks different, that might just have to do with caching.
The difference between CTRL + F5 and just F5 is that CTRL + F5 doesn't use your browser's cache, instead fetching everything fresh from the server, whereas just F5 uses your browser's cache. Your browser generally keeps track of when it cached things and will automatically fetch data anew if the time of caching was too long ago.
The former generally takes longer to load, naturally, which might be why the website looks different, at least until everything has been loaded.
Other than that, CSS gets a little weird sometimes, applying styles in a weird order. This generally has to do with the order in which, and where in your HTML document you actually load your stylesheets. Generally, loading all of them in the head of the document is a good idea. Complete redefinitions of styles in separate stylesheets can get very weird, even if it should follow normal precedence (Thread on CSS precedence)
Though, again, you'll have to elaborate on your problem further, maybe provide some screenshots, for anyone to be able to definitively help you.
I'm having a really weird behaviour with my TWA. When I am launching the app, the address bar is not shown and the app is running in standalone mode as expected.
But when I am switching between Apps (putting the app in the background), and coming back to it, something weird happens: the page reloads, and the address bar is shown at the top of my app. I am not really sure to understand what's happening here. Even more strange, it looks like this weird behaviour is not happening all the time.
Does anybody here encountered similar issues ?
I checked my assetlinks file, it's accessible and valid, app bundle and so on, everything looks fine. The fact that the app is not showing the bar at launch also seems to confirm that the problem is not coming from the certificate or a configuration issue. What else could cause the problem ?
First launch (looking perfect):
Back from background:
We have seen this occasionally as well.
Which version of Chrome Custom Tabs are you using? Seems like most articles/tutorials use e446d08 which is quite outdated. Suggest trying a newer/latest version of it:
https://github.com/GoogleChrome/custom-tabs-client/commits/master
Their last commit comment suggests that they are still testing things:
There's definitely more we can test, but this is a start.
https://chromium.googlesource.com/custom-tabs-client/+/da65829d7d4b80c00809c6c4aa7f61f88fc7ca26
im having a huge problem with the login node in the Web Browser. I click "Login" on the top right corner of my layout. It gets me to the login screen. All fine so far. Then im trying to login and as soon as i typed in my login-data and press "Sign in" Its just reloading the login-page. It doesnt take me back to the site i came from, it doesnt log me in, nothing. Im only having this issue in the web browser since it automatically logs you in, in the Notes Client. Thanks in advance.
PS: Sorry for the bad english.
Sincerly,
Brugen
Agree with Paul...
You could try: http://yourserver.com/names.nsf?open&login to check if your login is correct - disregarding any issues with your XPage.
Next, have a look at your server console to see if anything is written there to indicate a problem. If so it is easiest to use something like the XPages Log Reader to investigate the log files on the server. From the link there is a link to the project where you can download the database.
HTH :-)
/John
Sorry if this is assuming too little knowledge, but are you trying the correct username and password? By default Notes Client and web passwords are not synchronised, it's a separate HTTPPassword field in your Person document on the server. After changing, it may take a few minutes to take effect.
I m trying to setup a few image categorization tasks on Mechanical Turk sandbox developer version. When I try to view the HIT(the annotation image), it appears blank. I clicked on the 'Accept HIT' button but I still couldn't see anything.
In order to make sure that nothing was wrong with my project setup in particular, I signed in as a worker to accept HITS on other projects involving image categorization. I still continue to see a blank image in their categorization projects, where the image to be annotated is supposed to be displayed.
Can anyone help with this problem?Thanks.
Problem solved - it was a simple browser incompatibility problem.
I know you have already answered this for yourself, however for other requesters out there I think this may be useful.
I was developing HITs and I too was having issues view the HIT in Sandbox in Chrome and Firefox, I realized that it had something to do with the script being blocked by the browser and the way to fix this was to "unblock the content" - usually a shield icon in the URL bar.
When further developing my HIT I added information about how to see the HIT in the description box of the HIT so turkers could read the instructions and then work on the HIT - to be absolutely clear to the turkers, I added a "(READ DESCRIPTION)" in the title so turkers would know where to look.
Hope this helps!
I am experiencing a problem similar to 2 others who have recently written about this issue.
A newly created Page Tab Facebook app displays for admin users but not for regular users.
I only have 8 page tabs currently so it cannot be that there are too many.
Also, sandbox mode is disabled ( have tried both enabled and disabled).
Can anyone think of a reason that this might be occurring?
I added the tab with the code:
http://www.facebook.com/dialog/pagetab?app_id=YOUR_APP_ID&next=YOUR_URL
Could it have something to do with https in the url as opposed to http?
I am at a loss and do not know how to go about solving this issue.
Any ideas, however far-out they may be,would be aprreciated.
Thank you to anyone who might think they can help...
Have you forgotten to take the app out of Sandbox Mode? (try toggling it just in case, even if it's not in sandbox mode, as this is by far the most likely explanation here)
Also, check there aren't demographic restrictions set on the app or page via the API, as in this case only the users that meet the restrictions will see the tab. (though the admins will always see it)
Also check that you've configured the Page Tab URL and Secure Page Tab URL settings for the app correctly, as if a user uses HTTPS and the App doesn't support it they won't see the tab
If the tab isn't appearing at all it's almost certainly one of those two problems ,if it's displaying but the content isn't rendering, also check your code and make sure it's not fataling on checking the signed_request for non-admins or something like that