-
AuthorPosts
-
March 10, 2017 at 10:23 am #758787
Hello,
When I add
define( ‘COOKIE_DOMAIN’, ‘www.example.com’ );
//define(‘WP_CONTENT_URL’, ‘https://static.example.com’);
//define(“WP_PLUGIN_URL”, ‘https://static.example.com/plugins’);Enfold still refers to some content as https://www.example.com and not static.example.com
It’s like 50/50. When you view source half the links have static and the other half still have www
This creates a problem, when I want to have all the cookies served from only http://www.example.com and have all the refrences to links, static.example.com.
Please advise.
March 11, 2017 at 9:13 pm #759455Hey Nordmar,
This is because in your code above the last two lines are commitment out with “//” Try removing them.Best regards,
MikeMarch 11, 2017 at 11:14 pm #759490Hey Mike,
It’s commented out because it was causing problems,
I realize that // comments it out :DIf you try to do this on the enfold theme it will fail and give you ton of headaches.
The point is to avoid creation of more than 1 cookie.
Please advise how we can achieve this with enfold.March 12, 2017 at 3:16 am #759516This is directly related to “Use cookie-free domains”
Could you guys please make the tiny changes required to make the enfold theme a lot appealing to my clients.
Regardless of what the tests say, In the end if we can get this fixed up, I’m sure agencies and freelancers will greatly appreciate and use your product more in projects. I’m considering paying a little more for some of these themes that are at 96+ on the scores.Also WP-ROCKET plugin has some issues with your theme, The team has reached out to enfold author directly.
I hope you we all can come to a solution so I can keep recommending your product, Thank youMarch 16, 2017 at 3:37 pm #761989Hi Nordmar,
Are you using a single domain SSL certificate or wildcard? Can you provide a link to your website in private content, so that we can take a closer look.
Best regards,
VictoriaMarch 18, 2017 at 2:01 pm #762886We have wildcard domain.
Could you test this on your end?define( ‘COOKIE_DOMAIN’, ‘www.example.com’ );
define(‘WP_CONTENT_URL’, ‘https://static.example.com’);
define(“WP_PLUGIN_URL”, ‘https://static.example.com/plugins’);March 20, 2017 at 1:02 am #763397March 20, 2017 at 9:51 pm #763820If you try to use this in your enfold theme, it doesn’t work and breaks.
I believe this happens on all enfold versions.
define(“WP_CONTENT_URL”, “http://static.domain.com”);
define(“COOKIE_DOMAIN”, “domain.com”);March 20, 2017 at 11:51 pm #763909Example of error, Hidden for mods
define(‘WP_CONTENT_URL’, ‘https://static.auroraintelligence.com’);
define(‘COOKIE_DOMAIN’, ‘www.auroraintelligence.com’);March 20, 2017 at 11:58 pm #763913
- This reply was modified 7 years, 9 months ago by Nordmar.
March 22, 2017 at 5:17 pm #764901Hi,
did you check if this is happening with a default WP theme as well? please let us know about your results.
Maybe this helps: http://wordpress.stackexchange.com/questions/56629/serving-cookies-from-a-different-domain-or-sub-domain, as it sounds more like a general WP issue to me, than a theme related one.Feel free to make any feature requests for Kriesi here: https://kriesi.at/support/enfold-feature-requests/
Best regards,
AndyMarch 24, 2017 at 4:49 pm #766277It seems enfold theme has the issue.
I’m able to do this on Salient themeApril 19, 2017 at 9:52 pm #780169Any news about this ?
April 28, 2017 at 2:37 pm #784577Hi,
the error you posted earlier, is that the only one you get? Since this is not an enfold error. You would need to change the CORS setting of your server via htaccess.
Here is a tutorial about this: http://kriesi.at/documentation/enfold/enable-cors/
What’s basically wrong is that the domain that contains the font files does not allow “hotlinking” them on another domain. You have to change the settings of the static domain to allow thatIf you receive any other errors please post them as well :)
Best regards,
Kriesi -
AuthorPosts
- You must be logged in to reply to this topic.