I use wordpress with Wocommerce, integrates with paypal and stripe.

2012...ouch, scrap this one then....

@black3dynamite said in Wordpress Install - Page is trying to load unsafe script: @NashBrydges Change CustomLog /var/log/access.log combined to CustomLog /var/log/httpd/access.log combined Good catch. Thanks.

@bnrstnr said in WordPress behind NGINX Reverse Proxy issues: @scottalanmiller said in WordPress behind NGINX Reverse Proxy issues: https://mangolassi.it/topic/13062/install-a-basic-wordpress-site-with-wp-cli Doh, somehow I missed this. And this one.... https://mangolassi.it/topic/16084/installing-fedora-27-lamp-stack-plus-wordpress/

@brandon220 said in Using Vultr Apps for WordPress Hosting: I just loaded one to do some testing. Don't plan on using it for production. I may use Bluehost or Vultr on Fedora. My main reason was to get familiar with a theme and see if I like it. Then, I can destroy the instance and make it permanent and with the correct underlying OS. Works fine for that.

@bnrstnr said in Installing Fedora 27 LAMP Stack plus WordPress and SSL: @tim_g said in Installing Fedora 27 LAMP Stack plus WordPress and SSL: Create a new secure SSH key: ssh-keygen -t rsa -b 4096 -C "root-webserv1-key" Hit enter for default location and name. Hit enter again to skip passphrase creation. Now you should SSH to server to continue. Does this step disable normal logins or change anything at all? After my first restart my root password isn't working. This only generates a new certificate and does not do anything else. If your root password is not working, maybe you are typing it in incorrectly, or it's something else entirely, as what @NashBrydges is referring to. If you are using Putty, perhaps it's caching the old public key.

@wls-itguy said in Debian upgrade from 7 to 9 - no sub pages display now.: I'll see if I can explain this so there isn't any missing pieces. I upgraded our wordpress/debian 7 install to debian 8 and then to debian 9. At some point in there, not sure as I cannot recall if I tested the site working or not before moving on to debian 9 upgrade, the site is working but doesn't display anything below the main www. Example -> www.wls.wels.net works just fine but www.wls.wels.net/grow-in-grace gives me the big 404 error. I thought it had to do with permalinks inside Wordpress but that didn't fix it. Thought it could be a sites-enabled issue, that also was not the case. I am not sure where to go from here. From what I remember of websites, if you can get to the main site you should be able to get to the whole thing but I'm guessing not. What am I missing? Sounds like something in Apache to me. I know that isn't too helpful but it could be several things

Great

@scottalanmiller said in Installing WordPress on Fedora 25 and 26 Minimal install: For ease and speed and better management, I highly recommend using WP-CLI for all of your downloading, updating, configuration, etc. One like of WP-CLI will eliminate most of this installation, while making it easier to maintain in the long run. https://mangolassi.it/topic/13062/install-a-basic-wordpress-site-with-wp-cli Yup, that's what I use now, I won't every go back! https://mangolassi.it/topic/16084/installing-fedora-27-lamp-stack-plus-wordpress

@bigbear said in WordPress Hosting: Are you still doing hostadillo @scottalanmiller ? Yup, sure are!

Use Drupal. It's almost purpose built for this type of stuff. Custom content types and views make anything possible.

@wls-itguy said in MySQL/Wordpress issue: @scottalanmiller Yours? Yes, I PMd you a few minutes ago

@networknerd said in When Someone Points Their DNS at Your Site: @scottalanmiller said in When Someone Points Their DNS at Your Site: Could still be weird. But could be benign, too. Or it could be the NSA. All your websites are belong to NSA.

I have not found anything I liked. I am not leanging to jsut making this a section of my NodeBB. Maybe a dedicated page with the custom page plugin.

Wordpress Pros: Easy to setup Lot's of online support and pre-built customization Can be singular focused or multi focused site Cons: Target of hackers Updates of individual plugins or add ins may be required Ghost Pros: 1 Click install Fast and Focused blog Simple Cons: Less troubleshooting is available since it is less common Much less 3rd party customization.

Thank you, I'll investigate from here.

@tim_g said in Install a Basic WordPress Site with WP-CLI: @nashbrydges said in Install a Basic WordPress Site with WP-CLI: It allows me access when I set it up without https in the url. But once in settings, and I change the blog address from http://domain.com/blog to https://domain.com/blog I get the same too many redirects error. Cleared history and cache 3 times and still same issue. I'm going to blow this install away and recover from backup and will have to install manually. Still can't figure out why this issue. The root domain works perfectly with Let's Encrypt but as soon as I get to the blog folder it just shits all over itself. How did you set up the whole thing? Did you use my guide? It includes the SSL set up. I used your guide up to the SSL setup. I'm running a website in the root directory and Nginx as a proxy.

@masterarts said in 50+ WordPress Theme Frameworks For Developers & Designers: @Dashrender Please tell me what type of tags? I added them for you. Take a look at the ones that I used. It's at least a good starting point for useful tags. WordPress and "Web Design" are the two most critical tags for a topic of this nature. I was pretty torn using the "theme" tag, but I think it will prove to be useful.

@Breffni-Potter said in Slideshow wordpress theme: Sliders are the spawn of evil. Why do you need sliders? They increase load time, and really glitchy. Managing the one the devs put on our website is nothing but a pain. Looks nice tho, and keeping all the graphics slider images super super tiny doesn't hit load times to badly. At least it hasn't yet knock on wood

@tim_g said in Installing Wordpress on CentOS 7 Minimal: @jaredbusch said in Installing Wordpress on CentOS 7 Minimal: setenforce permissive; Setup SELinux permissions semanage fcontext -a -t httpd_sys_content_t '/opt/yourdomain(/.*)?' restorecon -R /opt/yourdomain semanage fcontext -a -t httpd_sys_rw_content_t '/opt/yourdomain/wp-content(/.*)?' restorecon -R /opt/yourdomain/wp-content I run my servers with SELinux running in Enforcing mode, not permissive. So if it's in enforcing, WordPress will not run correctly. Example, you can't update, and the Add Plugins page gives a connection error (it's because httpd can't write correctly due to selinux enforcing). Instead of running SELinux in permissive system-wide, you can keep it in Enforcing mode, and issue the following command: semanage permissive -a httpd_t The reason I use that one instead of by directory, is because I don't know how to do that... well I do, but I didn't have time yet to see what all directories need to be written to for updating and plugins pages and such to work correctly. I'll add that here some other time when I get a chance to look in to it more. I only said that for install message you remove it back to enforcing

Tried the above steps but seems to be not working until I able to discover there is a "greyed out" Live Chat slider button.

We only started using Yoast SEO recently.

@IRJ said in WordPress 4.7.1 Customizer Cannot Save: 4.7.1 is not the latest. 4.7.2 is the latest. WP 4.7.1 has some serious security flaws and an immediate update is highly recommended. It was a typo, actually was on 4.7.2.

@scottalanmiller said in Wordpress support troubles: @RojoLoco said in Wordpress support troubles: @scottalanmiller said in Wordpress support troubles: @RojoLoco said in Wordpress support troubles: @scottalanmiller said in Wordpress support troubles: Did you manage to get anywhere yet on this? I finally got the support form to work on my PC at home, so he filled it out and sent it. Hopefully it is sorted now. I guess I have to help clean out his PC at some point. LOL, sounds like he might be the source of many issues in the future. I saw a couple of posts on their support forum referencing similar issues. Seems like it might be widespread. Might be browser dependent or something like that. He couldn't get it to work in chrome or FF, I was able to get it to open in FF correctly. I think it is something else on his computer.

@BRRABill did you get everything answered that you needed for your WordPress project?

@scottalanmiller said in Wordpress on Vultr 768: @fuznutz04 said in Wordpress on Vultr 768: @scottalanmiller said in Wordpress on Vultr 768: @fuznutz04 said in Wordpress on Vultr 768: @scottalanmiller said in Wordpress on Vultr 768: @fuznutz04 said in Wordpress on Vultr 768: @scottalanmiller said in Wordpress on Vultr 768: Good reading, as well: http://www.smbitjournal.com/2011/02/why-we-reboot-servers/ A little modern design can get that to zero downtime no problem. Sure thing, but that would have been a huge undertaking in regards to how applications were written/designed. Starting fresh, no question. Would it? What are you running that wouldn't do that today? Wordpress will sure do that. Well, my comment was based on what the developers were telling me back then. Specifically, the way the websites (IIS & .NET) and databases (MS SQL) handle individual user "sessions". I'm not saying it couldn't be done, but it was more effort and development time than what the company was willing to invest in at that point in time. Oh, the developers screwed up and made a bad application that can't scare properly and then got stuck because scaling and transparent updates are done in the same way. Got it. But for WordPress, it "just works." More like, it was an older product that was built up over many, many years, and the products were being phased out anyway, and being replaced by a newer product that would scale properly. I left before said product came to market though. I have no complaints about Wordpress nowadays. Very simple to setup and use. Really a great tool for all user levels.

@stacksofplates said in WordPress Site Redirecting Sometimes to Hijacked Page: What's in your index.php file? I've looked through it before and must have just been stupid. There it was, a URLDECODE right in the middle. That was it!