I have a responsible theme in Drupal and when visiting my site on a mobile device I get a uncomplete view that is deformed. (In the beginning the mobile version worked)
When visiting the site on a mobile device, the site recognises the advice and makes the switch to the mobile site, BUT then I see that the mobile website is displayed like the this: red = mobile site, white = void
How it is at the moment
The idea is that the entire screen is red. :)
I used a different theme = same problem.
I uploaded a new version of Drupal = same problem.
Can you please help me :)
try using the default theme built into drupal 7. Make the theme "Seven" as the default and see if that resolves your issue. If that still doesn't solve your issue, try clearing your cache in drupal via admin > config > performance
If that still persists, try turning off cache on that page completely.
If all else fails install Drupal 7 with NO modules enabled and see what you get. Then turn on each module on one at a time and see how that goes.
Related
I am working on a news website, trying to implement amp. We are using Mobile_Detect.php to serve desktop pages to desktop and tablets, and mobile version to mobile phones and that works OK, our pages are mobile friendly according to Google for some time now, no problem.
Now, I started to enter the code for amp pages and encountered a situation I can' resolve. URL for the amp version have .amp at the end. Depending on the user's device, we are generating the page from the database and serving different pages to different devices.
Now, PageSpeed Insights and Mobile-Friendly Test shows that the page is mobile friendly but amp validator is pulling the desktop page, I can see by the source code it prints out, instead of a mobile page. I'm on the desktop, Chrome, but I'd expect it to work with mobile pages.
You can see that here: https://validator.ampproject.org/#url=http%3A%2F%2Fwww.poandpo.com%2Fbusineasdfasdfas-usual%2Fpublic-housadfadf-kong-972016223.amp
I installed Chrome amp extension and it says "AMP available" but when I click on it it also pulls the desktop version of the page and it's blank. I would expect the extension to load the mobile page but it doesn't.
We do have links canonical and amphtml, that's why the extension says there is an amp page.
So, how to tell validator to pull the mobile version of the page? The amp implementation is not done yet and I know there are some things missing, but without a validator is a bit hard to program.
Another interesting things is that when I open "Inspect" in Chrome and toggle to responsive design, it shows the mobile version of the webpage correctly. It also says "Powered by amp" and shows no errors although there are errors because we didn't even implemented all tags.
If anybody has any suggestion how to make amp validator to show the mobile page I'd appreciate that. Thank you.
I had a quick look at your pages but it appears that the amphtml reference but there appears to be a problem in the URL you are generating in the href= field. If you take a close look, the AMP URL is missing a '/'.
Broken: http://www.poandpo.com/business-as-usualmexicans-work-longest-hours-germans-the-least-97201645.amp
Works: http://www.poandpo.com/business-as-usual/mexicans-work-longest-hours-germans-the-least-97201645.amp
I created an app in Java in Eclipse on Google App Engine. For about a year now, I've had that app embedded in a google site iframe as a gadget. I added it using the "add gadget by URL" option and put in the URL of the app: https://mycompany-helpdesk.appspot.com (where mycompany is my company's actual name).
This has been working flawlessly for about a year. Recently I made a small change to the Java code, and it seemed like about a week after that change, the app will not display in Google sites anymore.
The app works just fine if I navigate straight to its URL https://mycompany-helpdesk.appspot.com.
I removed the gadget iframe on my google site and then tried to add it back, but the error I'm getting now is:
The gadget you added is not valid
Unsupported feature: org.apache.shindig.common.xml.XmlException: The markup in the document preceding the root element must be well-formed. At: (1,3)
I have a couple of these apps and I tried using the other one, but I get the same error. I've tried to add them on other google sites and even created a fresh one and still get the same error. I've spent days googling this but I don't think I've found anything that applies to my situation.
Did something change where suddenly it is not possible to do this anymore? If I can't embed the app this way any more, does anyone know of another way that I might be able to do this?
UPDATE: When I am editing the site, under Insert > More gadgets, if, instead of using the "Add Gadget by URL" link (which is what I've been using to insert this gadget) I use the "Include gadget (iframe)" gadget developed by Scott Johnston, then my apps will appear in Firefox and Safari, but not Chrome. This is not useful to me as our employees primarily use Chrome.
I think I'm just going to abandon Google Sites and redo the page in GAE. Hope this helps someone else who has been banging their head against their desk as I have been.
Update: I noticed that suddenly all the embedded apps on my test pages were working, so I reverted to an old version of the google site where the app was still embedded. Voila, it works again. Now if I can just figure out how to add in another embedded app I'll be good to go. It had been working in Safari and Firefox but that doesn't seem to be working now...
I'm a beginner with DotNetNuke and am having trouble debugging this problem. We are using DNN version 5.
On our local development machines our DNN site renders just fine. But we recently deployed to our test server and on there the site only renders fine when logged in as the Host. When viewing the site as just a normal visitor, all the styles are messed up -- it is just a white page with images gone and menus stacked vertically.
Clues / Notes:
We recently added a new .ascx and module
There are javascript errors, but it hard to tell what is causing them
You may ask about the Log Viewer screen. I looked there and I see exceptions, but I think the exceptions there are unrelated ( will look into this)
Works fine in our local dev environment
In server, only renders fine when logged on as Host
What are some steps I can take to try to debug this? Where else can I look besides the Event Viewer to see what is going on here?
Thanks!
What is the "new .ascx" that you deployed? Is that a skin page?
If something is wrong in the skin page and it is the default site page (under Admin > Site Settings), that would explain why non-admin users have issues, but Admin/Host users (where the site's Edit skin is working) don't have issues.
This solved it:
https://stackoverflow.com/a/3831419/614263
Due to permission settings it looks like IIS was blocking requests from the root to javascripts and css files. When looking at the Network traffic in FireFox I noticed that 404 errors were coming from "login.aspx?ReturnURL=../../blahblah.css"
Thanks for all your help and suggestions.
One of my DNN 7 sites has lost its ability to edit any of the pages. It now alway displays the Modules, Edit and Pages menu regardless if admin is logged in or not. When I try to edit a page, a window appears and then quickly goes away. There is nothing of use in the event log and I have tried different skins with no luck. I have another DNN website on the same computer and it works fine.
I have found that I am losing permissions to ToggleUserMode after I recompile a custom module that I'm developing has been installed on a test page and then recompiled in debug mode.
I'm wondering if this can be related to the fact that when I install DNN I blank out the default installation option of creating a dotnetnuke application. I leave that option blank and create the installation in the root of my website.
P.S I tried the amended module tag suggested on SO without any luck.
I finally figured this out. I had originally bound www.example.com to my default website but later created a new site for www.example.com. Apparently most of the requests were going to my new site, but the request for authorization for page editing was going to my old site which resulted in the 401 error. I rebooted my computer and disabled my default website and all is well.
I have installed the captcha module into my drupal 7 website and have it displaying on two forms. It is working properly other than it is caching the captcha so it is the same when I do a refresh. If I go into the admin and turn off the cache they are still the same but if I go and hit the clear all caches button it changes to a new one the next time I go to the page.
Anyone have any ideas? Thank You.
simple following 3 steps and you get out from your error.
uninstall captcha module.
clear catch history
go to module page and enable captcha module.
it will work for you.