Forum Replies Created
Appreciate the responses. Client decided to go a different way so there’s not need for a button.
Further to my findings, it appears that there may be an issue with the Database? It looks like one of the tables has a duplicate entry preventing the queries from working.
[Mon Mar 09 09:53:06.967342 2015] [:error] [pid 371] [client 220.127.116.11:61885] WordPress database error Duplicate entry ‘637496’ for key ‘PRIMARY’ for query INSERT INTO
autoload) VALUES (‘_wc_session_expires_3’, ‘1425953526’, ‘no’) ON DUPLICATE KEY UPDATE
autoload) made by shutdown_action_hook, do_action(‘shutdown’), call_user_func_array, WC_Session_Handler->save_data, add_option, referer: WEBSITE URL HERE
Thoughts on why this may have occurred and how to fix the issue?
P.S. The older version of Propulsion that’s installed works fine. I’ve given the theme a parent/child folders which are new names, etc.
Even the new Propulsion theme without leveraging the child them can’t save details.
I had to add width: 100%; to the .responsive.html_header_top.html_logo_center .logo class and it worked.
I tried that before, didn’t work. I just added it back as suggested above, still didn’t do it.
Thanks Ismael, you’re bang on about the nesting of the Div’s. I had incorrectly placed the wrap_all div.
Also, for the dynamic font, I’ve tried modifying it in the chile theme (added the css folder, copied the dynamic-css.php file but it doesn’t seem to be working?
Do I need to add anything to functions.php to have the dynamic.css.php file override the parent theme?
- This reply was modified 1 year, 8 months ago by kork.
I’m looking to change the grid to ‘sidebar’ => three and ‘content’ => nine alpha. With such small nav elements I’m looking to reduce the size. I know I could just adjust the width of the css but I’d rather make a “cleaner” change.
Hmmm, I could have figured that one out pretty quickly. I was more curious why it wasn’t working in the theme settings. Also, The drop down menu for the “About” section is appearing behind the main image. I’ve tried adjusting the Z-index to no avail. Also, when removing my child theme, the problem still exists.
April 12, 2014 at 2:24 pm in reply to: NextGen Gallery with Enfold background fade with Chrome not working #250526April 8, 2014 at 12:38 am in reply to: NextGen Gallery with Enfold background fade with Chrome not working #248547
- This reply was modified 1 year, 8 months ago by kork.
If I remove the line of code from the main theme avia.js file then it functions as I expect. However, following Ismael’s code does not seem to work. my child theme folder is not called “enfold-child” but it’s called “wgr-child”
Does the naming of the child theme matter?April 2, 2014 at 2:09 pm in reply to: NextGen Gallery with Enfold background fade with Chrome not working #246529
Sorry, I’m confused. Ideally, I don’t want to replace the default avia.js file in its entirety for a single line of commented out code. I’d rather just use Ismael’s solution if it’s just going to append the single line of code.
That said, my child theme folder is not named as the default. Is that why the modifications are not taking effect? How would I go about this keeping the child theme folder the same if that’s the case?March 31, 2014 at 1:02 am in reply to: NextGen Gallery with Enfold background fade with Chrome not working #245250
Hmmm, Also, the above code in the function.php file didn’t work either. I did take the avia.js file and put it in the child themes js folder.March 30, 2014 at 9:26 pm in reply to: NextGen Gallery with Enfold background fade with Chrome not working #245197
Chrome and Opera on Mac OSX Mavericks shows the issue. FF and Safari both work fine. On the default Enfold theme mentioned above, it’s only the second time the modal box is open and closed. It doesn’t do it initially.March 29, 2014 at 2:18 pm in reply to: NextGen Gallery with Enfold background fade with Chrome not working #244761
Hi Ismael. I appears that it has nothing to do with the Nexgen gallery.
It exhibits the exact same problem on the demo Enfold website at http://www.kriesi.at/themes/enfold/shortcodes/gallery/
I click on the thumbnail and it fades… Close it and open it again and no background fade.
Additionally, would there be a way to disable PrettyPhoto through the functions.php file? I’m using a child theme and don’t want to modify avia.js in case of future updates to the parent.March 28, 2014 at 7:28 pm in reply to: NextGen Gallery with Enfold background fade with Chrome not working #244540
Looks like the issue exists with the main enfold theme as well…
I click on the thumbnail and it shows the background… Close it and open it again and no background fade.
March 28, 2014 at 7:12 pm in reply to: NextGen Gallery with Enfold background fade with Chrome not working #244535March 28, 2014 at 5:35 pm in reply to: NextGen Gallery with Enfold background fade with Chrome not working #244488
- This reply was modified 1 year, 10 months ago by kork.
Ahhh, that’s the challenge. I don’t want to change anything in the parent theme except the custom.css file.
Child themes are very important to me as I’ve gone through what appears to be the Propulsion UTF-7 hack. Updating the theme also lost all of the custom code I had written. That was a couple years ago so much has changed, but child themes makes it much easier for me to separate my code vs. the theme code.
I would <thumbs up> changing it on the other themes also. I’ve used nearly all the Themes here (and love them) and have my clients purchase them directly now, but need an easy way to integrate custom code.
I still receive the same error…
Fatal error: Cannot redeclare avia_register_frontend_scripts() (previously declared in /home/www/public_html/wp-content/themes/child/functions.php:27) in /home/www/public_html/wp-content/themes/theme/functions.php on line 138
- This reply was modified 1 year, 11 months ago by kork.
I tried that before as well, but receive the error:
Fatal error: Cannot redeclare avia_register_frontend_scripts() (previously declared in /home/www/public_html/wp-content/themes/child/functions.php:22) in /home/www/public_html/wp-content/themes/child/functions.php on line 138