I am using the bitnami apps on bitnami cloud hosting server, and I have installed the Sugar CRM on my server. Now I want to install the Advanced Open Sale module to Sugar CRM for invoicing. But I am unable to install that, please guide me in the right direction how to do that.
The procedure that I am following is below:
Login to Sugar CRM
Go to admin section
Go to Module Loader under Developer Zone
after browse the zip file I am going to upload that, it works but it did not show me any uploaded module in the list.
may be there is some issue with the folder permission where it saves the file or any be there is some other issue. But it did not give me any error because it stop working after some time and did not get any error message.
any help would be appreciated.
Could you check if increasing the post_max_size and upload_max_filesize works for you?
http://wiki.bitnami.org/Components/PHP#How_to_modified_the_allowed_size_for_uploaded_files
File permissions are a big issue in sugar crm.
follow the advice in this article to ensure you have the correct permissions.
http://www.sugarcrm.com/kb/tag/file-permissions/
I also change the setting in the config.php file
'default_permissions' => array (
'dir_mode' => 1533,
'file_mode' => 509,
'user' => '',
'group' => '',
),
This seemed to work for me
Related
I am setting up a new TYPO3 Project for my company, this project is based on a previously existing Project, as the customer asked us to take it over. So I started with my company's kickstarter to create an empty but working Project. I then started adding the "old" content as well as the extensions used. Here I came across a problem: I added the news extension by Georg Ringer via composer and the frontend of the website showed the following Error:
(1/1) #1476045117 TYPO3\CMS\Extbase\Persistence\Generic\Exception\InvalidClassException
Could not find class definition for name "GeorgRinger\News\Domain\Model\DateTime
This could be caused by a mis-spelling of the class name in the class definition.
I found nothing about this online, checked my entire \ext-folder and didn't find anything related to this. I un- and reinstalled the news extension via composer but that didn't solve the problem either. I also have an issue, where I can't use the backend or the command line to flush my caches, so naturally I deleted the var\cache-folder and upon reloading my frontend I was prompted with another Error:
(1/1) #1580056272 TYPO3\CMS\Extbase\Persistence\Generic\Mapper\Exception\NonExistentPropertyException
The type of property GeorgRinger\News\Domain\Model\NewsDefault::eventStart could not be identified, as property eventStart is unknown to the TYPO3\CMS\Extbase\Reflection\ClassSchema instance of class GeorgRinger\News\Domain\Model\NewsDefault. Please make sure said property exists and that you cleared all caches to trigger a new build of said TYPO3\CMS\Extbase\Reflection\ClassSchema instance
I can still access the install tool as well as the backend. Clearing the cache doesn't change anything and my colleagues advised me to ask the TYPO3 community. This Project runs on TYPO3 version 10.4.12. Any and all help is appreciated, thank you. I am still very new to TYPO3, so please bare with me.
It turns out that there were two rogue DateTime's hiding in one of the non-composer extensions that were missing the \ before them. I also had to add to my ext_emconf.php the following:
'suggests' => [
'news' => '7.3.0-0.0.0',
],
Which also fixed the issue of me not being able to clear my cache, and upon reloading my frontend I saw content again.
Thank you everyone on here and Slack for the help!
After adding an empty text file called 'ENABLE_INSTALL_TOOL" in the 'typo3conf' folder the Install Tool is still locked when I visit hostname/typo3/install.php.
Some background information: I just uploaded all TYPO3 files to a remote host and am trying to get it to display the TYPO3 website. When I logged into the backend I got the following error:
1533822084 TYPO3\CMS\Core\Crypto\PasswordHashing\InvalidPasswordHashException
Configured default hash method
TYPO3\CMS\Core\Crypto\PasswordHashing\Argon2iPasswordHash is not available. If the instance has just been upgraded, please log in to
the standalone install tool at typo3/install.php to fix this. Follow
the wiki link for more details.
This error referred to this wiki page: https://wiki.typo3.org/Exception/CMS/1533822084
Here it is suggested to:
Call the standalone install tool and log in once. This should detect that argon2i is not available and will configure a different default hash mechanism. A backend login should be possible afterwards.
Which is what I am stuck on since the Install Tool is locked.
When you visit for the first time the address https://yoursite.com/typo3/install.php you should see the following screen:
As you wrote, you have to add a file ENABLE_INSTALL_TOOL (without extension) in the folder /typo3conf/ of your TYPO3 installation; the file can be empty.
After you have done that and refreshed the same page, you should see:
If you have not changed it (which is recommended) , the password should be the same password as the one of the first administrator user you have created during the installation.
If you have changed it and don't remember it, follow the on screen instructions.
Please refer to the official installation guide:
https://docs.typo3.org/m/typo3/guide-installation/master/en-us/QuickInstall/GetAndUnpack/Index.html
You need SSH access to your remote server. FTP or SFTP is not enough because the symlinks are not uploaded.
You need to transfer a zip- or tar.gz-file to the server and unpack it there. Never unpack them on your machine and transfer the files to the server.
I had same issue in Typo3 10 in CentOS 8
The argon2 password hash algorithm only in PHP >= 7.4, not in previous versions in CentOS 8.
In 7.2 / 7.3, argon2 is part of the "standard" extension and is disabled in RH build as libargon2 is not available in RHEL / CentOS
So if you can upgrade to PHP 7.4 it would work.
Alternative method when in PHP 7.3
in LocalConfiguration.php set
'installToolPassword' => '$2y$12$kB0JLQcbADywtxtxjoBoUOrCSk0RHhh/zuKDbFrtAYlr8fUlZ/1Em',
'passwordHashing' => [
'className' => 'TYPO3\\CMS\\Core\\Crypto\\PasswordHashing\\BcryptPasswordHash',
Open install tool ursite/typo3/install.php
password is 'password' (installToolPassword hash value above)
Now create an new admin and use that to login to backend and reset the passwords of other admins
I have a plain naked TYPO3 8 lts installation.
But I cant login with the backend user.
Install Tool works fine
When I create a new BE user in install tool it does not work as well ...
any ideas?
Check in Localconfiguration the [BE][loginSecurityLevel] and change it to normal if it is rsa
For me the solution was deleting the cookies from the browser, then login form works good.
I ran to a problem where I couldn't login to backend, even if I had [BE][loginSecurityLevel] set to normal. Nether did it work on a unix system or windows. The reason I found out was, because the extension 'sv' was disabled (not in PackageStates.php array).
So I went to PackageStates.php and added following to the array:
'sv' => [
'packagePath' => 'typo3/sysext/sv/',
],
Before that happened, I downgraded TYPO3 from 9 to 8. I was able to log in first, but not the next day, after the first logout.
This extension contains core default services.
Use the Debugger for your browser, e.g. Firefox Developer, and check if an error is given there.
Loading failed for the <script> with source “http://www.my-typo3-website.de/typo3/sysext/core/Resources/Public/JavaScript/Contrib/jquery/jquery-3.2.1.js”.
If you copy and past the above url into a web browser, you will see this outpu:
The requested URL /typo3/sysext/core/Resources/Public/JavaScript/Contrib/jquery/jquery-3.js was not found on this server.
The file name jquery-3.2.1.js has been abbreviated into jquery-3.js!
It can happen that the jquery used by the login form is not included as needed. This can happend by a Rewrite rule in the .htaccess file which transforms the filename jquery-3.2.1.js into a smaller name jquery-3.js which will not be found, because it simply does not exist on the file system.
At least you should try out the original .htaccess file named "_.htaccess" which is shipped with TYPO3.
Call to undefined function mb_convert_encoding(). How to install
mbstring extension installation on godaddy server?
I have found the solution. We need to complete the following steps:
1.Login to your server WHM as root
2.Search EasyApache or go to Software menu after that EasyApache
3. you can see there are some profile. click on customize profile default profile.
4. click on continue to second step
5. On “Step 2,” click on “Exhaustive Options”
6. Under PHP, check the checkbox for MBString
7. Proceed with Build & Compile Process
Make sure you wait for the build to complete.
I'm updating this thread as I went through a painful day trying to get this resolved. The mbstring extension is used by Magento (I needed it for 1.9) and without it installed, the checkout process will fail, with the shopping cart failing to take the user to the 'Thanks for your order screen' (although the order is sometimes created on the back-end successfully). It was also creating an issue when hitting the 'Send Email' button on the Admin panel on an Order, producing a 500 error.
In my log files, I was seeing the following error:
PHP Fatal error: Call to undefined function mb_convert_encoding() in
/home/yoursite/public_html/lib/Pelago/Emogrifier.php on line 556
Searching for this error gave results that suggested I needed to enable the mbstring extension on the server, but with a GoDaddy hosted virtual server, I ran into a wall of frustration with the package not being found via the php install search, and their tech support unable to assist. The above solution worked, although I will clarify the instructions below for the current WHM panel (Jan 2019):
Login to your server WHM as root.
Search EasyApache or go to the Software menu on the left and select 'EasyApache 4'.
You will see a list of profiles and at the top of the list, 'Currently Installed Packages'. Select the 'Customize' button.
Select the 'PHP Extensions' link or keep hitting 'Next' until you reach the page.
In the search box, type 'string', you will see 'php56-php-mbstring' and 'php70-php-mbstring'; move the grey slider on the right to install each.
Continue to the 'Review' tab. Here you can simply hit 'Provision' to install the extension. You can also save these options as a custom profile if you'd like.
After the build has completed, the extension should be available on all your domains.
Hopefully this will save someone some time trying to figure this out!
I'm working on setting up and migration of old sites to a new server from Dreamhost. I have 130 sites to migrate. 1 is successful. The version is: 1.12.1
The mods in the first site upgraded well. No problems. Have a procedure to migrate. That being said, the second site, as I followed my own documentation, fails when I try to access /admin/index.php
What I get is this below:
So, this is more informational than code... so please forgive me. I don't understand why CMS MADE SIMPLE is actually not simple.
That seems like an annoying issue. Forgive any repetition but here is what I would check:
that is is 100% functioning on existing server
correct php version 5.4.3+ (5.6+ recommended) on new server
that all files & database are copied fully & without errors
config.php settings are updated for new hosting & database
that .htaccess, php.ini/.user.ini settings are appropriate
check php error log
are there any additional modules installed that may require additional php modules
try more coffee or a nights sleep - both have helped me solve all sorts of issue in the past!
consider posting on CMSMS forum - will get a wider range of CMSMS users/experience and suggestions
Good luck
Chris
Not sure what process you are using. So presuming that the site was working correctly on existing hosting and that the new hosting meets recommended requirements, especially PHP version:
Export database
Zip/Compress all website files into a single file
Copy zipped file to new hosting
Create new database & user with full access
Unzip files and make sure that they are in the right location (probably website root)
CHMOD config.php to 0644 and edit database, username & password settings for new hosting, CHMOD back to 0444
Make sure .htaccess is using correct settings for new hosting
Login to admin and clear cache
Sorry that the instructions are so basic, but the process really is Simple.
Possible issues can occur if:
the PHP version is older than 5.4.3 (5.6+ recommended).
files copied individually using ftp and some are corrupted/not copied.
Apart from that it is pretty straight forward.
Hope it helps