I got a new computer and installed the latest XAMPP Version (3.2.1), which was quiet a change (they removed password controll). But the changes were not consistent because I can't start the FTP-Server from the control panel even though it is there, because the path to it is incorrect in some config file (not capitalized and with no space). It looks under
"C:\xampp\filezillaftp\filezillaserver.exe", but acctually it is here
"C:\xampp\FileZillaFTP\FileZilla server.exe" How can I correct this?
Related
PhpStorm 2020.1
Windows 10
Apache installed with XAMPP.
I am trying to get PhpStorm's built in server to recognize a document root. PhpStorm keeps running localhost:[port]/[project folder]/default.html. It should be running localhost:[port]/default.html
Because it keeps placing the project folder into the path, all the links fail.
I have edited the c:/xampp/apache/conf/httpd.conf file to change the document root and confirmed it in the console, that didn't work. Even setting the document root to the project folder didn't work.
It appears there is a setting or a different conf file that need to be adjusted, but I can't find it or figure out what is missing from the documentation.
Running the Config Wizard via the start menu (Windows 7) simply fails. Running it from the command prompt shows the infamous
'C:\Program' is not recognized as an internal or external command, operable program or batch file
I know this is due to the space in "Program Files" (dir C:\pro* /x doesn't show C:\Progra~1).
The solution I've found for this is to replace C:\Program Files\... with "C:\Program Files\...".
My question is this:
Since the WebLogic config wizard runs from config.cmd, which is loaded with variables for path names, do I have to update Windows system environment variable PATH and put quotes around all path names that have a space (since I don't know what WebLogic is looking for)?
Update:
I tried this and received Files was unexpected at this time. Which made me think I was off with the quotes, but they are paired properly around every path with C:\Program Files. A search on this error resulted with this advice...basically the double quotes are the cause.
If the lack of quotes causes the first problem, and the presence of quotes causes the second problem, what to do? It's a loop...
I installed another JDK in a location with no spaces (still got the error because I didn't change any environment variables because work site will change them back, breaking things).
The install docs in chapter 4 say:
To begin domain configuration, navigate to the
ORACLE_HOME/oracle_common/common/bin directory and start the
Configuration Wizard.
On UNIX operating systems:
./config.sh
On Microsoft Windows operating systems:
.\config.cmd
Which implied at a command prompt (to me anyways). I was reading another site for help and the guy said to update config.cmd to point it to new JDK location instead of JAVA_HOME.
Instead of right clicking on config.cmd to edit it I double clicked it and lo and behold...this nice domain creator GUI opened up where I could specify which JDK to use. Done! No errors...
If that little tidbit were in the docs it would've save me a lot of time and frustration. And no, I'm not a server admin type, just a dev who needed a local web server for testing purposes.
I hope this helps someone.
I want to enable LDAP module on my XAMPP Windows 10, here's the few solutions that I've tried :
Copy dll files to System and System32 and uncomment extension=php_ldap.dll in php.ini, both development and production.
Copy libsasl.dll to xampp/apache/bin
None of these working, when I opened phpinfo() there is no ldap info showing, which means the ldap hasn't been able to installed. I also added PHP in Windows Path with no success, but either my approach is wrong or that wasn't a solution. Any help appreciated.
Make sure the path\to\xampp\php directory has the following files
libeay32.dll
libsasl.dll
ssleay32.dll
Usually, you can find these files in path\to\xampp\sendmail - this library also uses them. But if not, try to search for them inside the xampp directory.
Uncomment or add the ldap extension in the php.ini (path\to\xampp\php\php.ini) file
extension=ldap
Restart the server
Make sure the path\to\xampp\php directory is set in the system environment variable PATH. To know how to do it, see this post.
I just ran into the same issue and the link you provided How to enable LDAP extension in XAMPP environment ended up being the solution for me.
I copied libeay32.dll and ssleay32.dll from C:/Ampps/php to C:/Windows/System32. I made sure neither of these files were in C:/Windows/System. From there I enabled extension=php_ldap.dll in the php.ini file. Ampps has a list you can enable php.ini dll's and if I remember right so does XAMPP. The last step is to just restart Apache and you should be good to go.
I'm using Windows 10 with Ampps instead of XAMPP but have to think they are pretty close.
I have a three year old or so MAMP install (a copy of the application folder and all its contents, databases, etc.) with a three year old MediWiki (version 1.19) installed on it, several pages, and a few images. I would like to know how I can access those pages (or at least the content on them) and import them or copy them over to a fresh install I made today with the latest versions of MAMP and MediaWiki.
I already tried copying the database folder (MAMP/db/mysql/my_database; contains .frm files) from the old install to the same location in the new install but it doesn't seem to have changed anything. I even looked at the contents of the tables with phpMyAdmin but I didn't find any of the old content. Where do I go from here?
I installed MAMP on my MacBook Pro running OSX Yosemite. I'm hosting locally (e.g. using localhost). I am able to install a fresh MediaWiki on my localhost MAMP server and it works fine (there's just no content).
UPDATE: After seeing this I changed $wgMainCacheType = CACHE_ACCEL to $wgMainCacheType = CACHE_ANYTHING in the MediaWiki local settings file and now I get an error page that looks like this:
Do I need to somehow upgrade my databases? They are old after all. How should I go about doing this?
Shutdown mysql
Just copying the MAMP/db/mysql/my_database is not enough
Copy the contents of your db folder and below to the new
MAMP db folder
Note i assume your new MAMP is pretty virgin
Poached it from here :
http://joejoomla.com/sound-off/157-how-to-upgrade-mamp.html
Start new mysql
Will incl necessary config files
It is not as if you should have expected MAMP to recurse directories
It needs config files from old and you don't have them yet
I have never done it on MAMP
Edit:
Concerning warning that resulted
Make sure that XCache is installed with the new version of PHP. The most likely cause is the new version of PHP simply doesn't have xcache installed. You can do this by creating a php file with just the code
<?php phpinfo(); ?>
and then viewing it in a web browser.
Setting $wgMainCacheType = CACHE_NONE; will disable all caching, which would prevent the error, but make things slow.
From: http://m.mediawiki.org/wiki/Thread:Project:Support_desk/%22CACHE_ACCEL_requested_but_no_suitable_object_cache_is_present.%22
Advice : for this kind of software, use a Virtual Machine, it will save your time : my own mediawiki is running for 8 years under debian, hosted on a several different Apple machines.
But for now, if you still have the former stack running :
0 . (always) save your database content + files
for the database :
https://www.youtube.com/watch?v=NnOE0KWHGkY
for the files :
tar cfvz my-old-mediawiki.tar.gz path-to-mediawiki-directory
This will allow you to rollback if something goes wrong
Export your content and history
go to the special page : "Export pages", list your pages.
if needed, use the special page : "List all pages".
this will produce an xml file.
Save your images somewhere on your file system
use the special page : "List all files".
you now have exported your pages and files
3) Switch stack
check that the new virgin mediawiki is working well
import your pages
go to the special page : "import pages", upload the xml file produced in step 1
you now have a similar wiki, minus the files
import your images :
after the step 4, each file page has been created without its content.
you can upload manually each image exported at step 2) if you have only some of them,
if that is too much files (>30), you can use this procedure : https://www.mediawiki.org/wiki/Manual:ImportImages.php
keep in mind also to reinstall any extensions installed previously.
I am trying to get a simple phpinfo() to print out on my local server (using MAMP). I made a new directory in /Applications/MAMP/htdocs (php_sandbox) and put a file in there named my_phpinfo with only phpinfo() in it. How can I view the contents of this file in my web browser?
Is it also advisable if I set the Apache document root to be in my home directory/sites? I will be mainly using this local server to test/host some small sites.
Thanks!
visit in your browser localhost/my_phpinfo/index.php assuming you named the file with
<? phpinfo();?> is in index.php. Also, make sure you are editing the correct php.ini in your MAMP directory by checking your mamp prefs and seeing what version of php MAMP is using.
Your in the right folder by default from what I remember. MAMP runs apache on port 8888 by default. You should be able to go to http://localhost:8888/ You can also get to this page via the control panel (should have a button to open home page). This page will also show you've configured MAMP's Apache to run on a different port.
Whatever you name your file; you'll want to give it a .php extension, so if you file is named my_phpinfo, add a .php so it becomes my_phpinfo.php. Make sure you function called is wrapped in php tags like so
<?php phpinfo(); ?>
If this file is directory in the htdocs folder you should be able to go to http://localhost:8888/my_phpinfo.php and get the PHP Info page.
As far is moving the directory. I normally do. Especially b/c it makes upgrading MAMP a little easier (already have to worry about MySQL). You might have to tweak the file permissions just a bit to make sure it runs correctly. I believe though you should be okay since it is running as your User.