I'm having a problem with a Drupal 7 install where pages keep loading.
The page will load and then repeat itself over and over until Chrome suggests killing the page.
It seems to happen at random times and there are no JS errors being reported or errors retrieving the page.
Anyone else had similar issues?
Modules include:
Panels
Views
Ctools
etc
This is usually caused by url aliases and/or url redirects doing some sort of circular definition. I've also seen this caused by login tobogin module setting up a circular redirect with something in the url redirect module. Find out which page is doing it and check your alieses and redirects for circular definition. It will probably be tricky to catch as it is usually two steps a -> b then b-> a, or something like that.
Related
I have a problem when placing an App module(v 8.4.8) on a page. When I placed an App module on a page I got a pop up saying "Had an error talking to the server (status 404). if you are an advanced user you can learn more about what went wrong - discover how on 2sxc.org/help?tag=debug".
This error happens on whatever action I try to do: trying to add and app, refresh page etc.
I checked a communication to the server using Firebug and seems that one of APIs are missing:
~/desktopmodules/2sxc/api/view/Module/GetSelectableApps
Referer: ~/desktopmodules/tosic_sexycontent/dist/dnn/ui.html?sxcver=8.4.8.19191
Did I missed something? Should I make some configuration after SexyContent module install (v 8.4.8)?
I just checked a video by Daniel Mettler where he showed how to install a module and seems that process is simple. Nothing to worry about.
Does anybody has any idea what might went wrong here?
The same actually happens when I install and Content module: Error about missing APIs:
~/desktopmodules/2sxc/api/view/Module/GetSelectableContentTypes
~/desktopmodules/2sxc/api/view/Module/GetSelectableTemplates
Thanks a lot for your time
My best guess is that it's an issue with the dnn domain/path configuration. So basically my guess is that
you have multiple domains, and if this is configured incorrectly, the paths in the js-calls won't fully match the original one
you have sub-portal (with paths like /products/) or something, and this isn't configured correctly in dnn
languages in portal-paths are causing similar issues.
So please compare EXACTLY the full base path and see if that's the issue.
I am working with Drupal (7) for the first time. I have installed it multiple times using both an automated Simple Scripts method, and a manual method. I am using the MERCI module to create a reservation system. Every time, over the course of several installations, a seemingly simple action - such as creating a taxonomy term (most recent trigger) or activating a standard module (Views for instance) results in a permanent 500 Server Error, interspersed with a properly loaded home page that will not allow the user to proceed to further links.
Check out the site here: www.browntv.org/mgmt
On first load - you will either get a Server Error, or a properly loaded page. If the page loads properly, clicking to ANY link should result in a blank screen, server error, or some other redirect.
I honestly don't even know where to start diagnosing this. I can't tell where an error (if there was one) would be logged, and nor can I figure out how to manually step my MySQL database backwards to try and remove whatever is causing the issue.
Any leads, suggestions, or ideas would be REALLY helpful. Until now, I've just been creating a new installation, thinking that the issue stems from installation issues. However it has happened so many times now I can't just keep starting from scratch.
I'm not seeing any errors on your site, and in fact it let me register a new account.
Having said that, as should be obvious from the error message, 500 is an internal server error, and no one is going to be able to determine the cause just by going to the public url. It's an error with a configuration file on your server. Generally a syntax error would give you a consistent, not a sporadic 500.
While I have a good deal of experience with MERCI, the way you've described the issue, that wouldn't have anything to do with it.
If the problem persists you should check your Apache error log.
Currently we are using a Kentico CMS for out web site and we used to have a page called pages/page1.aspx. We removed that page but every day the google, bing and yahoo sarch robot tries to read that page. Because the page doesn't exist the CMS throws the following error (in the log)
Event URL: /pages/page1.aspx
URL referrer:
User agent: Mozilla/5.0 (compatible; Yahoo! Slurp; http://help.yahoo.com/help/us/ysearch/slurp)
Message: The file '/pages/page1.aspx' does not exist.
Stack Trace:
at System.Web.UI.Util.CheckVirtualFileExists(VirtualPath virtualPath)
// and the rest of the stacktrace
When we get too many of these errors the whole site crashes (have to clear .Net temp files and restart app pool). Basically I can go to a page that doesn't exist, hit refresh many times and take the site down. Extremely bad. However, first thing, how can I get the bots to not try to access this page?
Thanks in advance.
If it's just a single page, or a few pages that are causing this, modify robots.txt to tell the legitimate search engines not to check it.
I'd also check what HTTP response you're sending when the page is not found? You might be sending something that causes the spider to think it should keep checking? Instead of a 404 maybe you should try permanently redirecting to your home page?
Finally, WTF? I'd talk to the Ketnico folks about this bug.
I think that you have a configuration error. While a robots.txt file would hopefully correct this issue, bots can choose to ignore that file.
A better solution would be to setup your error pages correctly. What happens when you go to a page that doesn't exist? It sounds like your system is showing a yellow screen, which is an unhandled exception bubbling all the way up to the user. I would check your error page setup so that users (and robots) get redirected to a 404 error page. I'm guessing that when Yahoo and others see that 404 page, they will stop trying to index it.
Have you tried using a robots.txt file?
I've had a drupal 5 site for over 2 years. For some reason my browser dropdown URL retains www.xxx.co.uk/node?destination=node for the site url. This has work until now - when I get
The page isn't redirecting properly
Firefox has detected that the server is redirecting the request for this address in a way that will never complete.
* This problem can sometimes be caused by disabling or refusing to accept
cookies.
typing in the bare url www.xxx.co.uk gives the same results. I'd just modified the site to add another picture gallery. I can access the site by typing in www.xxx.co.uk/node/1 but if I logout I'm back to the above problem, I assume for the same destination=node problem.
Didn't change any modules that I recall. Any ideas?
OK, I can answer this myself after a bit of investigation. I used import images to load my pics. What I failed to notice was that the nodes created by the import were all set to promoted to front page. Remove this from all the image nodes and everything is back to normal. No idea why my browser dropdown retains the url as above.
How can I get a module to redirect if a user doesn't have the correct permissions to view it instead of getting the usual "Access denied. You are not authorized to access this page." message?
If it is a module you are writing yourself use the goto function of Drupal
http://api.drupal.org/api/function/drupal_goto
If you are not writing it yourself then it's a bit tougher, you can set the error redirects with Drupal and some modules however for a specific module I think you might have to go in and patch it in some way.
pretty much anything you wanna do to modify drupal stock behaviour can be handled via hook_nodeapi
Custom Error provides the ability to easily customize 403 and 404 error messages. With that, you could use drupal_goto() to automatically redirect users, or drupal_get_destination() to build a login link that will return the user to the page they attempted to view.
For more general, login-specific functionality, you might check out LoginToboggan.
The source code for both modules will also include useful examples of how to approach this problem space if you do not want the overhead or external dependency of a module.