Forum Replies Created
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
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 3 weeks, 1 day 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 month 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
Anyone? If not, is there any idea when the theme will be updated to incorporate this new load order? I don’t want to modity the default functions.php file and then need to remember the change when I update the theme…
Actually, I figured it out. In the function.php file I set cropping to false for that image.
I just tried uploading an image that’s 920X410 and it cropped it to 920X375 ???
So something is forcing a crop of 35 pixels centered? And I can’t find it anywhere in the code? 920X375 is cropped to 920X340… 920X410 is cropped to 920X375… Very confused!February 11, 2014 at 3:36 am in reply to: What does the language file actually change? Having problems even just testing! #222015
YES!!! It was generating the files in the main theme folder, but placing them in the lang folder seems to have worked! Thanks!!!February 6, 2014 at 3:08 pm in reply to: What does the language file actually change? Having problems even just testing! #220466
When I created the spanish .mo file using the localization plugin, it created it in the root/languages folder and called it “avia_framework-es_ES.mo”
But it’s not actually using the translations provided in the file… This is very frustrating.February 5, 2014 at 2:54 pm in reply to: What does the language file actually change? Having problems even just testing! #219926
Okay, where are the .mo and .po files actually supposed to be once generated? I’ve found them in the root of the theme, but with enfold they seem to exist in the language folder in the root of content. I’ve opened the .po file with poedit and the changes I’m making are in the file.
But the theme is quite simply… not loading the translations. Any of them. it_IT, es_ES, it doesn’t matter. Not loading.February 4, 2014 at 5:04 pm in reply to: What does the language file actually change? Having problems even just testing! #219482
That was where I started as I’ve done this before with the enfold theme. Pretty simple stuff.
But for Propulsion, I took “Error 404 – page not found” the very first one in the list and set the translation to be “El Pago not Foundo” just to test it. The HTML reads “<html lang=”es-ES” class=”chrome chrome32 html_boxed “>
Nope, going to a 404 still shows the English version. I also tried the “Send” button for a form… Same thing. Doesn’t replace the text.February 4, 2014 at 6:22 am in reply to: What does the language file actually change? Having problems even just testing! #219199
That said, much of the site is now able to be in another language, but for things like:
this entry has 0 Comments
Is that something that needs to change in the source code, or can that be done with the language file?February 4, 2014 at 1:41 am in reply to: What does the language file actually change? Having problems even just testing! #219072
Yes, I have the WPML plugin installed. I’m just looking to be able to deploy a “spanish” version of “dutch version” or the website independently. I just want the default language to be one language. No switching, no multiple versions of posts…. Just a different language.
But I can’t see anything changing?
August 12, 2013 at 12:46 am in reply to: Utilizing Page Attributes with custom template in template builder? #134134
- This reply was modified 2 months, 2 weeks ago by kork.
It doesn’t work, that why I was curious if there was another method. No worries though. I’ll just build a custom page and instead. I just thought it would be nice using the template to use both types of elements.
Well I think I’m about to give up. I was told specifically by woothemes after troubleshooting that:
“This isn’t something specific to WooCommerce rather a side-effect of WordPress Menus and/or the theme you’re using.
Active categories _should_ have the “current-menu-item” class applied to them. You can see this if you add a category to your main nav and visit it with the TwentyEleven theme.
I can’t see a category in your sites navigation to check. Could you add one and activate TwentyEleven to see if there’s an issue in your theme.”
I enabled the twentyeleven theme and it worked perfectly fine and all of the page types had the classes applied to navigational elements. Enable Propulsion and voila, it disappears again.
The demo site at: http://www.kriesi.at/themes/propulsion/product-category/blog-theme/ is not working properly.
There is no current_page_parent class on the menu element on this category page. If you enable the twentyeleven theme, it works as expected.
@Nick – The links are still working (as per a few posts above).
http://www.tri-point.com/product-category/plastic-buckles/tensionlocks-ladderlocks/ does NOT contain the current-menu-item class on the active menu with propulsion as the theme, however, the twenty eleven theme does.
Sorry, didn’t see this until now.
You can see that there is no class applied to the active menu items
But the main category page and the product page does have the current class applied:
TwentyEleven theme applies the classes to all of the pages above.