<div>
1) Run WordPress + SugarCRM out of 2x different directory hierarchies. 
 
Call the WordPress install blog.foo.com + the SugarCRM install crm.foo.com or something like this, where you're 2x different code bases are in 2x separate directories. 
 
2) SugarCRM 7.11.4 or below will work on PHP-7.2 + docs page suggests SugarCRM 7.11.5 requires PHP-7.3, so if you're starting from scratch, start with PHP latest, which today is... 
 

<pre><code class="code-1 nolinks" id="code-20-42987360-1">lxd: net16-template-lamp # php --version
PHP 7.3.12-1+ubuntu18.04.1+deb.sury.org+1 (cli) (built: Nov 28 2019 07:37:16) ( NTS )
Copyright (c) 1997-2018 The PHP Group
Zend Engine v3.3.12, Copyright (c) 1998-2018 Zend Technologies
 with Zend OPcache v7.3.12-1+ubuntu18.04.1+deb.sury.org+1, Copyright (c) 1999-2018, by Zend Technologies
</code></pre>
 
3) WordPress will work with any PHP-7.X version. 
 
4) Better to build a directory hierarchy outside /var/www/html. 
 
I normally use /sites/$project/$site/wordpress for WordPress installs. 
 
Anything outside /var/www/html will work, as /var/www/html is technically owned by the packaging system so some future update might overwrite files in this directory. 
 
5) No changes are required to your wp-config.php file... unless you're doing something very odd... 
 
6) You said, &quot;The database has been copied into the same MySQL server that the SuiteCRM is stored in.&quot; 
 
If you mean you've actually created SugarCRM tables in your WordPress database... this... to me... is a horrible idea, related to long term maintenance. Better to have 2x separate databases, as the the backup systems for each have no clue about the other. 
 
In other words, Wordpress has no clue about SugarCRM + SugarCRM has no clue about WordPress. 
 
If for example someone runs some brain dead WordPress database cleaner (most cleaners are highly brain dead), then all your SugarCRM tables will be seen as orphaned... or non-WordPress tables + could potentially be dropped. 
 
I've had to fix this type of nonsense before. Then it happens a great deal of time + money are required to get a site running again.
</div>

<div>
Thanks David, very helpful information. 
 
4) I'll push the wp site into the path you have suggested. 
 
6) You said, &quot;The database has been copied into the same MySQL server that the SuiteCRM is stored in.&quot; 
 
No problems there, it is in a different database, named differently ; and shows up if you are at the database level in &nbsp;Navicat. 
 
Cheers 
Bernard
</div>

<div>
Perfect! 
 
Sounds like you're on track! 
 
Be sure to also setup a similar path for your CRM. 
 
For my projects, I'd use... 
 

<pre><code class="code-1 nolinks" id="code-20-42987556-1">/sites/$project/blog.foo.com/wordpress

/sites/$project/crm.foo.com/sugar
</code></pre>
 
Where project relates to the common project both these relate to, which could also be a client name. 
 
My target, since I work with 1000s of sites is to be able to know at a glance, exactly what site is running in what directory + exactly the code for the site. 
 
Where site is either a domain name or host name.
</div>

<div>
Hi David, Thanks for the extra detail, &nbsp;I have created a path as below: 
 
I have sanitised my actual domainname with 'mydomainname' 
 
/&lt;root&gt; 
&nbsp; &nbsp; &nbsp;/bin 
&nbsp; &nbsp; &nbsp;/boot 
&nbsp; &nbsp; &nbsp;/dbc_mydomainname &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(no '.com' at the end) 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;/blog.dbc_mydomainname.com 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; /wordpress 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;/crm.dbc_mydomainname.com 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; /suitecrm 
&nbsp; &nbsp; &nbsp; &nbsp;/dev 
&nbsp; &nbsp; &nbsp; &nbsp;/etc 
et al 
 
Is this what you mean? 
 
I can access suitecrm with this url mydomainname.com/suitecrm/ ; 
 
but with WordPress I get &quot;No webpage was found for the web address: <a href="http://mydomainname.com/wordpress/" rel="ugc">http://mydomainname.com/wordpress/</a>&quot; 
 
From here can you point me to an effective installation process that will install a dummy website? &nbsp;I.E. step1; step2 etc. 
 
 
 
Cheers 
Bernard
</div>

<div>
Hi David, 
 
I have edited the wp_options in &nbsp;the database to show the following: 
 
siteurl &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="http://mydomainname.com/connections/blog.mydomainname.com/wordpress" rel="ugc">http://mydomainname.com/connections/blog.mydomainname.com/wordpress</a> 
home &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="http://mydomainname.com/connections/blog.mydomainname.com/wordpress" rel="ugc">http://mydomainname.com/connections/blog.mydomainname.com/wordpress</a> 
 
Is this correct? 
 
I gather I need to have the .htaccess with both WP and suitecrm sections in it? 
 
The .htaccess file should reside in the <a href="http://mydomainname.com/connections/" rel="ugc">http://mydomainname.com/connections/</a>&nbsp;folder? 
 
Cheers 
Bernard
</div>

<div>
File Layout - Looks good. This allows you or anyone else working on these sites to instantly know what code is running where. 
 
Host Names - Your hostnames seem off a bit. 
 
For me, I'd setup.... 
 
1) crm.foo.com to serve the /dbc_mydomainname/crm.dbc_mydomainname.com/sugarcrm files. 
 
2) blog.foo.com to serve the /dbc_mydomainname/blog.dbc_mydomainname.com/wordpress files. 
 
So avoid the /wordpress + /sugarcrm in your actual URLs. 
 
You'll accomplish this by setting your Apache DocumentRoot directive to a file path for each host - blog + crm.
</div>

<div>
Tip: If you actually edited your database changing wp_options then your WordPress site will be unstable (no guess now it will work). 
 
WordPress database editing requires using <a href="https://wp-cli.org" rel="ugc">https://wp-cli.org</a> or some other <a href="https://www.php.net/manual/en/function.serialize.php" rel="ugc">serialized data</a> aware tool. 
 
<a href="https://www.php.net/manual/en/function.serialize.php" rel="ugc">serialized data</a> requires a mechanical/software tool to make edits. 
 
Unsure if SugarCRM requires a similar tool. 
 
You should never, ever, ever reference directory paths in your siteurl + home variables. This is done via Apache, never WordPress. 
 
Both siteurl + home should be set to <a href="https://blog.foo.com" rel="ugc">https://blog.foo.com</a> + nothing else. 
 
Random Aside: Starting sometime this year using HTTP rather than HTTPS will trigger a suspicious site message in all browsers. 
 
100% of your sites, at this point, should be - HTTPS + HTTP2 + Brotli - for best visitor experience. Be sure to use HTTPS enhancements of HSTS + OSCP Stapling for highest performance.
</div>

<div>
Hi David, 
 
Thank you for your patience. 
 
Clearly I was misreading your instructions when you indicated to set things like: &quot;/sites/$project/blog.foo.com/wordpress&quot;. &nbsp;I had always thought 'foo.com' was a placeholder for the real domainname and you were implying I should replace the 'foo.com' accordingly. 
 
However in reading your latest notes, I gather the ApacheServer picks up the request to 'mydomainname.com' &nbsp;(my substituted domainname) &nbsp;and redirects this to the local server address 'crm.foo.com' and serves up WordPress content from there? 
 
From this, for a single site instance for both Suitecrm and WP, then I would have the instance code implemented in the following path structure. 
 
/&lt;root&gt; 
&nbsp; &nbsp; &nbsp;/bin 
&nbsp; &nbsp; &nbsp;/boot 
&nbsp; &nbsp; &nbsp;/blog.foo.com 
&nbsp; &nbsp; &nbsp;/crm.foo.com 
&nbsp; &nbsp; &nbsp;/dev 
&nbsp; &nbsp; &nbsp;/etc 
 
Is this correct? 
 
Cheers Bernard.
</div>

Database Engineer

Bernard Bailey

<div>
Thank you David, 
 
For your comments and suggestions. 
 
Cheers 
Bernard
</div>

<div>
You're welcome! 
 
Glad you got this working!
</div>

<div>
<div class="content wysiwyg-content">
I need to migrate my wordpress site to reside on the same UBUNTU 18.04 server with SuiteCRM running PHP Version 7.2.19-0; Ubuntu 18.04.2 
 
I have a /var/www/html directory on the target server where the suitecrm folder is located. 
 
I am not sure where I restore my wp-admin, wp-content &amp;&nbsp;wp-includes directories and wp-*.php files. &nbsp;Do these get copied to this /var/www/html/ folder and update the refs in the wp-config.php file? 
 
The database has been copied into the same MySQL server that the SuiteCRM is stored in.
</div>
</div>

I need to migrate my wordpress site to reside on the same UBUNTU 18.04 server with SuiteCRM running PHP Version 7.2.19-0; Ubuntu 18.04.2

I have a /var/www/html directory on the target server where the suitecrm folder is located.

I am not sure where I restore my wp-admin, wp-content & wp-includes directories and wp-*.php files.  Do these get copied to this /var/www/html/ folder and update the refs in the wp-config.php file?

The database has been copied into the same MySQL server that the SuiteCRM is stored in.

Migrate Wordpress alongside a SuiteCRM site on UBUNTU 18.04 server

SugarCRM produces the web application Sugar, a customer relationship management (CRM) system that is available in both open-source and commercial open-source applications. Sugar's functionality includes sales-force automation, marketing campaigns, customer support, collaboration, Mobile CRM, Social CRM and reporting.

SugarCRM

PHP is a widely-used server-side scripting language especially suited for web development, powering tens of millions of sites from Facebook to personal WordPress blogs. PHP is often paired with the MySQL relational database, but includes support for most other mainstream databases. By utilizing different Server APIs, PHP can work on many different web servers as a server-side scripting language.

Ubuntu is an open source software operating system that runs from the desktop, to the cloud, to all your internet connected things.

Ubuntu

WordPress is a free and open-source content management system (CMS) based on PHP and MySQL for creating websites and blogs. Features include a plugin architecture, a template system and strong management, customization and search systems; through its dynamic presentation of content, webmasters have the flexibility to create websites easily.

WordPress

Linux is a UNIX-like open source operating system with hundreds of distinct distributions, including: Fedora, openSUSE, Ubuntu, Debian, Slackware, Gentoo, CentOS, and Arch Linux. Linux is generally associated with web and database servers, but has become popular in many niche industries and applications.

Linux

Kernel programming for Linux operating systems can be done with many different languages; C, C++, Python, Perl and Java, which are some of the most common languages used.There are also many different varieties of Linux, such as Ubuntu, Fedora and OpenSUSE.

Linux OS Dev

A Linux distribution is an operating system made as a software collection based on the Linux kernel and, often, on a package management system and are available for a variety of systems. A typical Linux distribution comprises a Linux kernel, GNU tools and libraries, additional software, documentation, a window system (the most common being the X Window System), a window manager, and a desktop environment. Most Linux systems are open-source software made available both as compiled binaries and in source code form, allowing modifications to the original software. Over three hundred distributions are in active development, including commercially backed distributions (such as Fedora, openSUSE and Ubuntu) and community-driven distributions (such as Debian, Slackware, Gentoo and Arch Linux).