Hi I have installed a Wordpress theme in my MACBOOK pro successfully (after downloading MAMP & creating wordpress database of course).
When i open localhost:8888/wordpress - it all looks good. I am now trying to open this link: localhost:8888/wordpress/wp-admin to be able to customise the theme. I encounter error.
The error in safari says: "Safari can't open the page because the server unexpectedly dropped the connection).
Here is the image
I have tried all trouble shooting guides i found and they DID NOT WORK:
- Changing the speed in my apache setting
- Remove cache in my safari (Safari > Preferences > Privacy > Remove all website data)
- Clean up my MacBook to free up 4gb of RAM
- In my terminal command: sudo purge
Please help! My goal is to be able to open: localhost:8888/wordpress/wp-admin and customize the theme in my local computer.
Here are steps to fix this...
In Safari
Menu bar > Preferences > Privacy > Remove all website data
On prompt select
Remove Now
All cookies will be cleaned up & now test your website is working or not.
It should start working as normal.
Hope this helps.
Related
The URL of the blank page > http://localhost:8888/phpMyAdmin5/?lang=en&language=English
Another try via > http://localhost:8888/MAMP/ to MySQL (phpMyAdmin) > http://localhost:8888/phpMyAdmin5/ ... also a blank page ... !?
Mamp Pro 6.x
PHP 8.x
MacOS 12.6
What's happening here and can it be solved?
There could be many factors for the issue. First, clear your browser cache and try it again. If it does not help, I'd recommend trying following:
Examine the error logs: Inspect the Apache and PHP error logs for any
errors. By selecting the "Open Log" button in the "Apache" or "PHP"
tab of the MAMP interface, you can access the error logs.
Examine the configuration options: Make the "config.inc.php" file's
configuration values are accurate. The "phpMyAdmin" directory in the
MAMP application folder contains this file. The host, port, and login
credentials may need to be changed, among other variables.
Time limits: Increase the max execution time and memory limit values in the php.ini file.
If none of these help, you might want to reinstall MAMP and see.
I've installed XAMPP (control panel 3.3.0) on my Windows 10 PC. I then installed VS Code (v1.74.3)
I ran the phpinfo() and pasted the results into the Xdebug wizard and followed the instructions on that page (downloaded php_xdebug-3.2.0-8.2-vs16-x86_64.dll, renamed as php_xdebug.dll and saved to C:\xampp\php\ext)
I then added the following to C:\xampp\php\php.ini file.
zend_extension = xdebug
I restarted the Apache server and VS Code. I also installed the PHP Debug (v1.30) extension to VS Code.
When I load up a test PHP file and try to debug it, it seems to work as expected in VS Code (it stops at breakpoints, I can step through, the variables pane updates, and echo'd text appears in the debug console. This is when I do "launch currently open script").
But when I do "launch built-in web server", to see what it looks like in a browser, it opens Chrome to http://localhost:62xxx/ (the number changes each time) and the page says:
Not Found
The requested resource / was not found on this server.
I've probably just missed a setup/config step somewhere. How do I get it to open a browser that shows what the script is outputting?
My situation:
I have 10 typo3-websites running on two servers:
First Server (apache with php 5.6.32):
typo3 versions: 6.2.3, 6.2.4 and 6.2.14
Second Server (apache with php 7.0.26):
typo3 versions: 7.6.14 and 8.7.1.
I'm not able to open the page on an iPhone or iPad with osx 10.x or above. I tested it on safari, chrome and firefox, but I get always an error like:
"[browser] can't open the page (...) because the server unexpectedly dropped the connection. (...)"
On a mac (osx 10), I get the error only in safari 11.0.2, but not in firefox or chrome.
I can open the pages without any problems, if I'm logged in at the typo3-backend with the same browser.
A Wordpress-Page is also running on the second server without any problems.
I have no problems on windows, android or other linux machines.
I tried the following without success:
clearing the typo3 cache
using the default .htaccess
using an empty .htaccess
The solutions from this site (german!): http://www.typo3forum.net/discussion/79617/ios-10-3-1-laedt-seite-nicht
Any ideas?
Have you tried to set the header content-length to 0?
https://docs.typo3.org/typo3cms/TyposcriptReference/Setup/Config/Index.html#enablecontentlengthheader
Try to set the following lines to your TypoScript
config.enableContentLengthHeader = 0
You say you can open the page if you are logged in that matches the following description:
If the Backend user is logged in, this is disabled. The reason is that
the content length header cannot include the length of these objects
and the content-length will cut off the length of the document in some
browsers.
i have been using MAMP PRO and xdebug for years (through Netbeans) and suddenly I am unable to debug. I have narrowed the issue down to the following. Whenever I append the parameter XDEBUG_SESSION_START=anyvalue to the localhost url the page freezes, and obviously, Netbeans just waits for a connection.
for example, the following url works fine:
localhost:8888/index.php
this url freezes:
localhost:8888/anypage.php?XDEBUG_SESSION_START=netbeans-xdebug
I have tried:
-closing all copies of Netbeans.
-restarting MAMP PRO.
-restarting the Mac.(Mavericks)
-deleting MAMP temp files in /Applications/MAMP/tmp/php
-creating a new MAMP host ..ex localhost1
nothing seems to fix the problem. There is nothing wrong with the php.ini file, or Netbeans config, or xdebug config. I am desperate.
To be clear, when i restart the computer, start MAMP PRO and nothing else (Netbeans is not running), then go here in ANY BROWSER---
localhost:8888/anypage.php?XDEBUG_SESSION_START=netbeans-xdebug
the page does not load and just waits.
other examples the following DOES load
localhost:8888/anypage.php?XDEBUG_SESSION_ST=netbeans-xdebug
the following DOES NOT load
localhost:8888/anypage.php?XDEBUG_SESSION_START=netb
what is blocking the connection when the get parameter "XDEBUG_SESSION_START" is added??? I am ready to give up.
Fixed this by changing one line in the php.ini file from:
xdebug.remote_host=localhost:8888
to:
xdebug.remote_host=127.0.0.1:8888
I have no idea why it worked with localhost for years, and all of a sudden did not. I suspect the installation of Xcode, but cannot prove or disprove.
I downloaded the Aptana_Studio_Setup_Linux.zip package, unpacked it and run ./AptanaStudio. It starts fine, but reports one problem:
The embedded browser widget for this editor cannot be created. It is either not available for your operating system or the system needs to be configured in order to support embedded browser.
After that, it opens the "Welcome page" in external browser (Mozilla), but when I click on a link to install PHP support it does not open the destination target. No wonder, because the link is in format: com.aptana....etc. I.e. written in reverse. I assume such links only work with internal browser.
If I look into details, I get these error messages:
No more handles [Unknown Mozilla path (MOZILLA_FIVE_HOME not set)]
org.eclipse.swt.SWTError: No more handles [Unknown Mozilla path (MOZILLA_FIVE_HOME not set)]
at org.eclipse.swt.SWT.error(SWT.java:3400)
at org.eclipse.swt.browser.Browser.<init>(Browser.java:138)
at org.eclipse.ui.internal.browser.BrowserViewer.<init>(BrowserViewer.java:224)
at org.eclipse.ui.internal.browser.WebBrowserEditor.createPartControl(WebBrowserEditor.java:78)
at com.aptana.ide.intro.browser.CoreBrowserEditor.createPartControl(CoreBrowserEditor.java:138)
at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:596)
at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:372)
at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:566)
at org.eclipse.ui.internal.PartPane.setVisible(PartPane.java:290)
etc. I hope this is enough.
I tried to set the env. variable:
export MOZILLA_FIVE_HOME=/usr/lib/mozilla/
However, it only changes the error message to:
No more handles [NS_InitEmbedding /usr/lib/mozilla/ error -2147221164]
org.eclipse.swt.SWTError: No more handles [NS_InitEmbedding /usr/lib/mozilla/ error -2147221164]
at org.eclipse.swt.SWT.error(SWT.java:3400)
at org.eclipse.swt.browser.Browser.<init>(Browser.java:225)
at org.eclipse.ui.internal.browser.BrowserViewer.<init>(BrowserViewer.java:224)
at org.eclipse.ui.internal.browser.WebBrowserEditor.createPartControl(WebBrowserEditor.java:78)
at com.aptana.ide.intro.browser.CoreBrowserEditor.createPartControl(CoreBrowserEditor.java:138)
at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:596)
at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:372)
For start I really want to have PHP working, but I'd also like to fix the whole internal browser issue in the end.
I happened to come across this: https://groups.google.com/forum/#!msg/xmind/5SjPTy0MmEo/PbPi0OGzqPwJ
Which advised running:
sudo apt-get install libwebkitgtk-1.0-0
should solve the problem. It worked for me so I figured I'd share here.
FWIW, I ended up here while trying to get the Play! Framework working on Ubuntu 13.04. using the Scala-IDE. So far, everything seems to be working...
You need to download and install XULRunner from mozilla.org, and point MOZILLA_FIVE_HOME to that directory.
After installing xulrunner you need to set this:
MOZILLA_FIVE_HOME=/usr/lib/xulrunner
You will have to install XULRunner then edit the eclipse.ini.
After installing xulrunner, adding the following line in the eclipse.ini solved the problem of "No more handles" issue.
-Dorg.eclipse.swt.browser.XULRunnerPath=/opt/eclipse/xulrunner/
I am using eclipse 3.63 and ubuntu 12.04.
Edit: getting internal browser to work is NOT required in order to get PHP support in Aptana. Just install PHP support from Help, Software updates menu.
If this is the problem I think you're having, just installing Firefox 2 (alongside FF3) should fix the issue. It happens because Aptana can only use FF2 at the moment. Hopefully they'll fix this soon.
If you're on Ubuntu, it's really just a case of:
sudo apt-get install firefox-2
Naturally, the process will vary on different distributions.