Obsolete Releases > SME 8.x Contribs
Wordpress 4.3.1 on SME 8.1
guest22:
Maybe we need to ask Stephane to adapt the contrib to have a db entry that holds the wanted path... That should not be a huge task.
devtay:
--- Quote from: guest22 on November 06, 2015, 12:02:32 AM ---Maybe we need to ask Stephane to adapt the contrib to have a db entry that holds the wanted path... That should not be a huge task.
--- End quote ---
Good idea. I'll send the email request now.
janet:
devtay
--- Quote ---.....just need the final little bit to get the main domain to be served from /usr/share/wordpress.
--- End quote ---
In an earlier post in this thread, I said:
"You can move the code from /opt/wordpress to the ibay/html folder.
You will need to change/correct config files & any template/custom template settings to match & remove aliases that were created by the templates to allow web access to /opt/.....
Look in the rpm for smeserver-wordpress & you can see all the files that are created when it installs, use mc to view it or the rpm command."
So copy the contrib rpm to your server (ie the smeserver-wordpress), use mc to view the rpm package.
In there you will see all the various files created when the rpm installs.
Typically you would be looking for the template that contains the alias fragments.
Change those or better still create a custom template with the changes, & your domain should point at the wordpress site.
devtay:
--- Quote from: janet on November 06, 2015, 06:58:18 AM ---devtay
In an earlier post in this thread, I said:
"You can move the code from /opt/wordpress to the ibay/html folder.
You will need to change/correct config files & any template/custom template settings to match & remove aliases that were created by the templates to allow web access to /opt/.....
Look in the rpm for smeserver-wordpress & you can see all the files that are created when it installs, use mc to view it or the rpm command."
So copy the contrib rpm to your server (ie the smeserver-wordpress), use mc to view the rpm package.
In there you will see all the various files created when the rpm installs.
Typically you would be looking for the template that contains the alias fragments.
Change those or better still create a custom template with the changes, & your domain should point at the wordpress site.
--- End quote ---
Thank you for pointing this out to me again. I'll give it a shot. I'm going to keep track of the changes that get made along the way and update the wordpress wiki page just in case I'm not the only one needing to do this.
stephdl:
--- Quote from: devtay on November 05, 2015, 11:43:20 PM ---I'm a little stuck and need some help. I've looked at the httpd.conf file and I know what changes need to be made to it in order to make the main domain serve the /usr/share/wordpress/ directory instead of /primary. I've even changed it manually and restarted apache and verified it will work. I expanded the template again and have my default httpd.conf file back. I just manually changed it to verify my thoughts were correct.
I'm looking at the templates located at /etc/e-smith/templates/etc/httpd/conf/httpd.conf. I believe the file that creates the line for the DocumentRoot is contained in /etc/e-smith/templates/etc/httpd/conf/httpd.conf/80VirtualHosts but I can't figure it out. It looks like the information should be stored in the domains database but it's not listed with db domains show. Where in the heck is that line coming from?
--- End quote ---
--- Code: ---# db domains show junco.es
junco.es=domain
Content=ola
Description=mailman
Nameservers=internet
--- End code ---
ola is my Ibay as documentroot
--- Quote ---I also modified /etc/e-smith/templates/etc/httpd/conf/httpd.conf/92wordpress and added code similar to the code found in http://wiki.contribs.org/Web_Application_Redirect_Tutorial. I created a wordpress property called domain and stored the domain I want to redirect there. The template change worked and added a new <VirtualDomain> directive with the correct DocumentRoot. However, apache didn't use it. I can't find in the apache 2.2.3 docs anything about precedence of <VirtualDomain> directives but it seems like once there's a declaration, apache ignores any similar directives.
--- End quote ---
I suppose that you have restarted httpd-esmith instead of apache ?
--- Code: ---sv h /service/httpd-e-smith
--- End code ---
does the domain you want to use is not already in use in the domain database ?
--- Code: ---As mentioned, I do know the changes that need to be made to the documentroot, but I can't find the point to make the change. Any push in the right direction or explanation will be greatly appreciated.
--- End code ---
please let your modification there
--- Quote ---The direction I'm going in is:
1. Find the way to change the documentroot for the primary domain on the server.
2. Remove the Rewriterule for /wordpress
3. Change the directory directive for /usr/share/wordpress to allow symlinks, indexes, and AllowOverride for .htaccess.
--- End quote ---
This is valid remark/nfr I did some of them for the dark side of the force, I could rewrite the template and let you the abilities to add your fragment inside the template, idem for AllowOverride
but at the end :)
I wonder why you don't start from scratch with the wordpress webapp in an Ibay....
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version