Peelman: Https://www.skyverge.com/blog/how-to-override-woocommerce-template-files/

Messel: Horacsio: THAT IS NOT AN ANSWER TO MY QUESTION!

Harsh: Everywhere I see this: copy from this: woocommerce/templates/single-product/price.php to this yourtheme/woocommerce/single-product/price.php.

Wisman: Horacsio: So you guessed?

Ottomaniello: Horacsio: so I am asking you. what are you basing it on?

Delfuente: Horacsio: I am asking this so I dont have to go out and find the answer myself.

Dusak: I just followed the instructions! to copy from the woocommerce plugin templates to my own theme under woocommerce

Marmas: Horacsio: but nevermind because i found the answer myself because, like i said, gettting info from you is like PULLING TEETH

Engert: Im gonna move on with my work

Gomaz: LindsayM_: I’m trully sorry : I am. honestly. and thank you for being so patient.

Campanile: LindsayM_: but it’s only mytheme/woocommerce?! no subfolders?

Schellhase: Horacsio: i am going to recommend you work on a live server because you’re not very good at communicating what you’ve done and what you need to do. At least if you could give people a link, they can get those answers for themelves

Arnwine: Horacsio: wading through this mire that is your communication skills is just fatiguing.

Bobo: When I replace a file with a new one in a child theme, it has to have the same folder structure in the child theme as it has in the parent theme right? I dont quite get how I then have to reference that file, the codex says require_once get_stylesheet_directory . ‘/my_included_file.php’ ; does this go in functions.php ?

Zampieri: It gives me this error http://gymn2016.apps-1and1.net/news/

Layfield: Why are you doing a require of a css

Kohr: Because I tweaked a css file in my child theme

Aguado: Is that not how it works?

Layfield: You dont require it, you enqueue it

Ratel: OK WTF is going on with my wordpress

Bertagnolli: I was logged into it today and now I cant get in at all

Veller: Rontill: https://codex.----escape_autolink_uri:a03ded6cd97ffffa8f7b4e1454f3eecc----.org/Function_Reference/wp_enqueue_style

Nordeen: BOGO: what makes you think wordpress is doing something against you?

Dethlefsen: BOGO, did you forget your p***word? you’ll need to specifically identify the problem for anyone to help

Layfield: Rontill name it something other than theme_enqueue_styles

Layfield: Child_theme_enqueue_styles

Chandrasekara: Now its giving me another error

Czarny: OK I cant login at all to my sites as it says the crappy cookies

Lauterborn: Http://i.imgur.com/QpSjXrt.png

Aust: It eventually loads but first displays this message

Sciascia: BOGO: Please attempt to disable all plugins, and use one of the default Twenty* themes. If the problem goes away, enable them one by one to identify the source of your troubles.

Samowitz: Http://asylum.rocks/wp-login.php?redirect_to=http%3A%2F%2Fasylum.rocks%2Fwp-admin%2F&reauth=1

Dalee: See I dont have any themese other than the one I use installed

Bornemann: ERROR: Cookies are blocked or not supported by your browser. You must enable cookies to use WordPress.

Nordeen: Rontill: that’s not what fris told you to do.

Nordeen: BOGO: go ask who is managing this for you: Apache/2.4.16 Unix OpenSSL/1.0.1e-fips mod_bwlimited/1.4 PHP/5.6.13 Server at asylum.rocks Port 80

Nordeen: WordPress doesn’t give 403’s. httpd does.

Warden: Where you getting that at?

Kesterson: Where did you get that error from

Nordeen: Http://asylum.rocks/wp-login.php

Nordeen: You don’t have permission to access /wp-login.php on this server.

Nordeen: The server configuration itself is denying, not wordpress