Topic: Wordpress 4.3.1 on SME 8.1

[TerryF]

I don't know where to start

[TerryF]

No flame intended, directness can be a weakness I know

Might have been a little coffee deprived, I can assure you if a flame had been intended there would have been no doubt what my intention was

Good luck with your projects.

[devtay]

Ok. Understood to everyone's replies. I'm going to add my name to the grumpy list. Chalk it up to my sense of humor being turned off. Getting pressure here from the boss and the developer at this point.

I'm going to take a break then get back at it after lunch. I'll take a fresh look at things then and report back the issues I'm running into.

[Stefano]

you are welcome (in grumpy list too )

[TerryF]

Ah its all part of being human now enough of the warm and fuzzy stuff..

I was not aware of the excellent contrib by Daniel of FWS that HF mentioned,
http://wiki.contribs.org/Webapps-common

Had I been I would have also recommended it. Having had a look it would appear to do what you want and with a lot less effort and worry than with the tutorial I mentioned.

[janet]

Devtay

You would hope big people read things the discussion section of that How To is also a must read for an alternative way

l

Not sure I understand exactly what you mean by this remark.

To say it another way
Adults should read the available document fully & completely, including attached pages eg the Discussion tab

devtay I think your response is quite uncalled for, you should not blast anyone the way you did to Terry just because he said you should read the whole document. He was helping you to find other information that you may have overlooked.

I am now asking you to apologise & withdraw your  unpleasant statement IMMEDIATELY.

There is no place at all here for the comments you just made. Keep your emotional sensitivity to yourself & refrain from having outbursts in this forum. Thank you.

[devtay]

Ah its all part of being human now enough of the warm and fuzzy stuff..

I was not aware of the excellent contrib by Daniel of FWS that HF mentioned,
http://wiki.contribs.org/Webapps-common

Had I been I would have also recommended it. Having had a look it would appear to do what you want and with a lot less effort and worry than with the tutorial I mentioned.

Appreciate it and I agree about the webapps. I'm working in that direction now. Have decided not to reinvent the wheel and use the wordpress contrib. There is much more functionality to it than the iBay install method at this point and I'd rather have standard packages installed than a custom one for future updates. I told the developer to live with the slightly older version of wordpress. I think the webapps-common contrib can still work even though the wordpress contrib installs wordpress to /usr/share/wordpress vice /opt/. Will report back once I have had a chance to fiddle with it. Thanks.

[devtay]

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?

I also spent some time working with webapps-common but I can't get it to change the primary domain. It just adds <VirtualDomain></VirtualDomain> directives outside of the directive for the primary domain.

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.

I'm going to use the SEF URL suggestion in http://wiki.contribs.org/Joomla to modify the <Directory> directive to work with wordpress so that is the last piece. Until I get a solution to the DocumentRoot though, the rest doesn't matter.

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.

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.

[guest22]

You can change your primary HTML domain to any ibay content by default in server manager...

[devtay]

You can change your primary HTML domain to any ibay content by default in server manager...

Yup. Have done that a ton of times. However, the wordpress contrib installs to /usr/share/wordpress. I guess this would be a "custom" entry for the main domain on the server. I've got wordpress up and running just need the final little bit to get the main domain to be served from /usr/share/wordpress.

[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]

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.

Good idea. I'll send the email request now.

[janet]

devtay

.....just need the final little bit to get the main domain to be served from /usr/share/wordpress.

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]

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.

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]

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?

Code: [Select]

# db domains show junco.es
junco.es=domain
    Content=ola
    Description=mailman
    Nameservers=internet
ola is my Ibay as documentroot

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.

I suppose that you have restarted httpd-esmith instead of apache ?

Code: [Select]

sv h /service/httpd-e-smithdoes the domain you want to use is not already in use in the domain database ?

Code: [Select]

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.
please let your modification there

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.

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....