Forum Replies Created
Same here! Jake got back to me instantly which took me by surprise at how quick he was to respond and gave me instant suggestions right off the bat. Incredible support and assistance! Best support I’ve ever had hands down.
Resolved! Thanks! And review added 😉
Hello, it appears that none of your documentation pages are working at the moment…
Thank you so much! This is EXACTLY what I have been dreaming of and you just made my dream come true!!!Forum: Reviews
In reply to: [User Switching] Should have a shortcode or widget
What an excellent solution to display it in the footer if admin bar is hidden. I’d highly suggest updating this review to 5 stars 😉
That worked!!!! Look at that, you said completely untested and because you are the pro you are, it didn’t even need to be tested, it worked the first time around! Thank you very much for your quick response and solution. You are awesome and I love this plugin!
Does anyone have a suggested fix for this? Thank you!
Thanks Tarelking for your response!
The wp_enqueue_script reference pointed out that for scripts, I need to use a different function reference than the wp_enqueue_style.
(Keep in mind that the style.css file I am referencing below is the stylesheet that was created by HTML5 Up. I am putting this in a separate location than my themes stylesheet)
It turns out that the prefix in the init.js was pointing to “css/style” where “CSS” is the folder and “style” is the stylesheet, with the extension “.css” automatically being added. So essentially, the path was “http://website.com/css/style.css”.
By changing the prefix in init.js from “css/style” (roughly line 38) to “wp-content/themes/theme_name/library/css/libs/style”, the code is now pointing to the correct location which looks something like this: http://website.com/wp-content/themes/theme_name/library/css/libs/style.css
You could also do the follow by adding it to your global scripts.js file or in the header.php:
Oh my gosh! I am having the EXACT same issue!!!! It is driving me crazy…
What I believe is happening is that within the “init.js”, starting at line 45, the “breakpoints” for some reason are looking for the root of the website and then trying to look for files located in a css folder.
Although this is good for static files, in WordPress, it needs to point to, for instance, (../wp-content/themes/theme_name/library/css/helios.css).
There has to be a way to tell the js files to point where you want it to go in WordPress besides automatically pointing to a css folder in the root by default. Any ideas how to go about manipulating this process? Hope this helps!
Thank you danieliser! The reason
<a href="#">Open Modal</a>was not working was because the option “Sitewide” under General Options was set to “NO”. I changed it to “YES” and this fixed the problem.
Now I am trying to figure out how you can specify what page to load the script on when you decide to set “Sitewide” to “NO”.