Edit: Sry for spam.. I can browse from backend -> Web -> View
I'm new to Typo3. I installed 7.3 on apache on ubuntu 14.04. When I install the Introduction Package from the backend Admin Tools -> Extensions -> get preconfigured distribution, I can 'View Webpage' and see the fault site, but all the feature descriptions dont work. They refer to /typo3/typo3_src-7.3.0/features/ when they should refer to id=35 (in LTS I could access these trhough URL's.)
I'd love to browse these locally without manually entering URL's instead of the official page.
Any help is apreciated, thanks for the effort.
You need to enable the Apache module mod_rewrite and make sure that the file .htaccess exists in your root directory. Or you can disable the TYPO3 extension realurl.
Related
What are the other option to upgrade PHP Version to latest without affecting other Sub domain
I'm complete new to the server side configuration.I'm working on a project setup at testsubdomain.mydomain.com Which need to use latest versoin of PHP 7. I tried AddHandler AddHandler application/x-httpd-php72 .php .php5 .php4 .php3 it is not working. Our cpanel does not include PHP Version Manager.How to upgrade PHP Version without affecting other sub domains
Better to update your cpanel version to the latest one as well as update Easy Apache 3 to Easy Apache 4 which will then have the PHP multi manager facility with which you will have the PHP 7.x version installed and you can easily change the php version for a specific domain.
You can't. It is because your are using people services. Especially cPanel, it is control by user account. The PHP version is bind to the user account. This is how cPanel works. https://documentation.cpanel.net/display/EA4/PHP+Home#PHPHome-Vendor-providedPHPversions
If you want different version in one server, I suggest you have a dedicated server or VPS then installed with docker. Like that you have different PHP version environment.
I have installed TYPO3 Version 7.6.15 by using composer and also I am using the Xampp version 7.0.0. I have installed many extensions and activated them successfully at the backend of my TYPO3 page.
Now, I have installed the Ecodev/typo3-cms-speciality-distribution via composer. and i am trying to activate it from extension manager but it is giving me following error. Error
Now, I have no idea, what to do? at this link https://github.com/Ecodev/typo3-cms-speciality-distribution
it is written to deactivate EXT:fluid_styled_content, EXT:context_help, EXT:func, so i did, but still the same error. Any help will be grateful thanks.
Finally, i found the error, it is just because when we installed the speciality distribution package, we also need to install and activate all the other dependencies which are important for this package.
After installing them, this problem will resolved. As, i was using it via composer mode.
Thanks
I read that it was impossible to install yii2 on a standard hosting platform (redhat, centos...) without deleting the AssetManager.
And install is lock with it. Access refused, permission denied.... Despite the rights 777 on the assets folder.
And in default way, hack code, disable control like (is_writable) to allow continued the install process to congratulation, but without css ....
But I can't modify all the code , to use it?
They're a lot of issue about assetmanager.
I tried yii1 few years ago, and it was wonderful framework... But everything is permitted under windows. Someone tried to install it under redhat, fedora, Centos.
There is a specific configuration ... Or yii2 not builted and designed for theses environments ?
Because i found tuto about laravel 5.1, Zend 2 since 2013... But nothing about Yii2, and only one... about Yii1... on this hosting OS.
Yii2 is ready for professionnel standard hosting environnement or is just for hobbist with Wamp under Windows ? (Online tuto is in majority on this OS, with Wamp...).
And maybe for that, it's work fine... like i test under windows
Thank you for the links. I had read
Finally I found the answer, which is never explained in the tutorial above (because often disabled and the module is not present in Ubuntu or Debian)
It's SELinux security. To install Yii2 there are the following commands:
semanage fcontext -a -t httpd_sys_rw_content_t 'each folder writable'
setsebool -P httpd_unified 1
Without this open rignt, you can't install Yii2
All what Yii 2.0 requires is a Web server supporting PHP 5.4 or above.
( currently not PHP 7 due to reserved word conflict that will be solved in future releases )
And yes 5 stables versions ready for production has been released, currently Yii 2.0.5
Here is a quick example about how to install Yii2 with CentOS6 which has nothing different from what is already described in the official docs.
If you know any CentOS related issue please post them and we will discuss answers, because sincerely i just did few searches and didn't found any besides few wrong apache or nginx configurations or missing packages like this CentoOS7 case. Otherwise if you need a pre-configured & working VM with Yii2 and CentOS 7, then you may check this vagrant repo.
I am using Windows Vista Ultimate and I want to install Umbraco CMS, with which I have no previous experience.
Common installation methods i.e. Installing either via Microsoft Webmatrix or Web Platform Installer didn't work for me. The former is for 7 and 8 versions of Windows and the latter downloads all installation files but fails to install. That is it shows "Installing ..." dialog for over 3 hours that makes me to forcefully end the installation. So all efforts have to be done from scratch (including download of the installation components using Web Platform Installer).
Is there a way to manually install Umbraco without the help of Platform Installer? I have downloaded seperately the files needed for Vista(e.g. Umbraco 7xxx.zip,Powershell 2, ASP.NET MVC, etc.). I don't see any executable in the package for Umbraco. There are just DLL's which I don't know where to copy to, as well as many aspx and ascx files that I don't know what to do with.
http://our.umbraco.org/contribute/releases shows the latest and all other available umbraco releases.
Under the 'Current' heading, you will find links to the most recent stable release detail page where you can grab UmbracoCms.X.X.X.zip which are all the files you need to go through the process manually.
One of the absolute best things about umbraco is that it's so easy to spin up a new isntall this way!
Important! Before you unzip - be sure to right-click the .zip file and open the properties page.
There will be an option to "Unblock" - be sure to click this or you may well experience issues with the dlls.
Unzip these files to where your webroot will be, set-up your IIS site and open in your browser - umbraco will automatically pick up that you need to do 'the install' and take you through a few simple steps that set-up the database and your admin credentials. There are no exe's or installer files - it's all embedded, more-or-less, in the site.
A good practice is the remove the [/install/] folder once you've gone through these steps.
Umbraco has some installation documentation here if you want to see all the various ways and steps available to install an umbraco site. -I prefer the .zip way described above, but you can also go the NuGet route too.
I installed WeBlog package from sitecore marketplace (http://marketplace.sitecore.net/en/Modules/WeBlog.aspx) in my sitecore instance. Initially i had trouble installing package however i retried again deleting weblog.config file. It installed without any issue however when i look into content editor i don't see any WeBlog Modules under Template, System or Layout sections.
Does anyone know why?
Thanks.
Which version of Sitecore are you on? Is the module compatible? Weblog shows that it's compatible with the following versions: CMS 6.2, CMS 6.3, CMS 6.3.1, CMS 6.4, CMS 6.4.1, CMS 6.5.
Assuming you're on a compatible version, I'd check to make sure the layouts and sublayouts that were in the weblog package were actually installed on your instance. Open up the zip file and check out what files should have been installed.
Failing that, have a look at the log files to see if there are any glaring errors.
As a last ditch, you may want to try publishing. It shouldn't really matter in your content editor view, but I view the "publish" feature of Sitecore like the "reboot" feature of Windows.