Forum Replies Created
-
AuthorPosts
-
Hi!
Please try to increase the allocated php memory and set it to 128M. Open up wp-config.php and below the php tag:
<?php
insert this code:
define('WP_MEMORY_LIMIT', '128M');
Cheers!
PeterHi!
1) It’s definitely no theme issue because I can reproduce it with any other theme on your server and no other Enfold user reported this issue. You can test this by yourself, switch to TwentyThirteen (default WordPress theme) and then try to open this page: http://www.caffechiriatti.ch/my-account/edit-address/billing – you’ll still get the “Not found” error.
2) You’re using an outdated WPML. Please install the latest version of WPML (which has the version number 3.1.7.x) and update all the WPML extensions. Then install this plugin: http://wordpress.org/plugins/woocommerce-multilingual/
Regards,
PeterSeptember 8, 2014 at 5:59 pm in reply to: WordPress 4.0 Upgrade Easy Slider / Post Slider Issues #315241Hi!
Great, glad you could solve the issue.
Regards,
PeterHi Wils1234!
Please add this code to the quick css field or child theme style.css file:
#top .av-magazine-time{ text-transform: none; }
Cheers!
PeterHey!
Yes, maybe that’s the reason – but we can’t say it for sure without knowing the error message. You can also try to deactivate all plugins – maybe a plugin is incompatible with WP4.0.
Best regards,
PeterHi!
chrislaver – please create us an admin account and post the login credentials as private reply.
Best regards,
PeterHey!
You can also try to use W3TC instead of super cache.
Regards,
PeterHi Erdogan!
Um ehrlich zu sein ist dies nicht leicht machbar. Soweit ich weiß können Plugins wie Formidable dabei helfen so etwas zu realisieren, aber ich habe es weder selbst ausprobiert, noch können wir dbzgl Support anbieten. Es würde daher uU ein Freelancer/Entwickler benötigt werden um diese Funktion zu realisieren.
Regards,
PeterSeptember 8, 2014 at 5:47 pm in reply to: A technical question about Masonry Gallery under "Media Elements" #315226Hey!
We use ajax to query the next set of images when the user scrolls down. The image query can be found in wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/masonry_entries.php (function called “query_entries_by_id”).
Regards,
PeterHi stevemulisa!
1) Please update WPML to the latest version. You’re using version 3.1.5 with is not compatible with WP3.9 or WP 4.0.
2) Please update all other plugins too, including WooCommerce
3) Update the theme to Enfold 3.9.2
4) Update WordPress to 4.0.
Then try to re-create the pages with WooCommerce and check the results.
Best regards,
PeterHey tgdigitalsolutions!
You (or someone else) modified the enfold/js/avia.js file somehow. We don’t support customized code thus I replaced it with the original code and the slider works now. I made a backup of your custom code – you can download/view it here: http://pastebin.com/XdrUKrpA
Best regards,
PeterHey!
I’m not seeing any errors – did you solve the issue? If not please post your login credentials and we’ll check the admin page.
Regards,
PeterHi!
Dann füge bitte diesen Code in die enfold/functions.php oder child theme functions.php ein:
function avia_custom_taxonomy_in_body_class( $classes ) { if(is_single() && get_post_type(get_the_ID()) == "portfolio") { $custom_terms = get_the_terms(get_the_ID(), 'portfolio_entries'); if($custom_terms) { foreach ($custom_terms as $custom_term) { $classes[] = 'portfolio_cat_' . $custom_term->slug; } } } return $classes; } add_filter( 'body_class', 'avia_custom_taxonomy_in_body_class' );
Dieser fügt zu den Body Klassen noch die Portfolio Kategorie hinzu (bzw besser gesagt den Slug der Kategorie). ZB für Produkte wird der Slug vermutlich “produkte” sein, sodass der Code wie folgt aussieht:
.single-portfolio.portfolio_cat_produkte .header_color .main_menu ul:first-child > li#menu-item-134 > a { color: #333333; } .single-portfolio.portfolio_cat_produkte #menu-item-134 a .avia-menu-fx, .single-portfolio.portfolio_cat_produkte #menu-item-134 a .avia-menu-fx { visibility: visible; opacity: 1; }
Für Referenzen gibt es eine andere Menu Item ID und Slug:
.single-portfolio.portfolio_cat_referenzen .header_color .main_menu ul:first-child > li#menu-item-132 > a { color: #333333; } .single-portfolio.portfolio_cat_referenzen #menu-item-132 a .avia-menu-fx, .single-portfolio.portfolio_cat_referenzen #menu-item-132 a .avia-menu-fx { visibility: visible; opacity: 1; }
Cheers!
PeterHi!
If you add this code to enfold/functions.php a theme update will overwrite it – yes. However you can create/use a child theme if you don’t want that the custom functions.php file is affected by a theme update. Just create a file inside the child theme folder, call it “functions.php” and add your code into it. You can also download the sample child theme here: http://kriesi.at/documentation/enfold/using-a-child-theme/
Cheers!
PeterHi Gurify!
You hided the flags with some custom css code in the quick css field:
.language_it, .avia_current_lang, .language_en {display: none!important;}
I removed it and now the flags display as intended.
Best regards,
PeterHey Richard!
We can’t access this page without an admin account (“You do not have permission to preview drafts.” error).
Best regards,
PeterHi!
Great, glad the update solved the issue :)
Best regards,
PeterHi!
Great :)
Cheers!
PeterHey David!
Please post a link to the page where you want to change the background color.
Cheers!
PeterHey blauwoog!
1) Please make sure you’re using the latest theme version 2.9.2. If not please update the theme. See: https://vimeo.com/channels/aviathemes/67209750
2) Maybe a plugin is incompatible with WordPress 4.0. Deactivate all plugins, clear the browser cache and try to use the widget areas again.
Best regards,
PeterHey danielpaullucas!
I fixed it. I simply re-created the page.
Best regards,
PeterHey!
You need to update the entire framework folder (enfold/framework) including all sub-folders and files in it. The best solution would be to use ftp and to simply overwrite all files.
Best regards,
PeterHi!
Please try to deactivate all plugins – maybe one or more plugins are incompatible with WP4.0.
Best regards,
PeterSeptember 6, 2014 at 11:55 am in reply to: Icon box icons not displaying in several browser instances #314462Hey!
It seems like your server uses the wrong mime types for the font files. If you’re using an apache server add this code to the htacess file:
<IfModule mod_mime.c> # Audio AddType audio/mp4 f4a f4b m4a AddType audio/ogg oga ogg opus # Data interchange AddType application/json json map topojson AddType application/ld+json jsonld AddType application/vnd.geo+json geojson # JavaScript # Normalize to standard type. # http://tools.ietf.org/html/rfc4329#section-7.2 AddType application/javascript js # Manifest files # If you are providing a web application manifest file (see the # specification: http://w3c.github.io/manifest/), it is recommended # that you serve it with the <code>application/manifest+json</code> media type. # # Because the web application manifest file doesn't have its own # unique file extension, you can set its media type either by matching: # # 1) the exact location of the file (this can be done using a directive # such as <code><Location></code>, but it will NOT work in the <code>.htaccess</code> file, # so you will have to do it in the main server configuration file or # inside of a <code><VirtualHost></code> container) # # e.g.: # # <Location "/.well-known/manifest.json"> # AddType application/manifest+json json # </Location> # # 2) the filename (this can be problematic as you will need to ensure # that you don't have any other file with the same name as the one # you gave to your web application manifest file) # # e.g.: # # <Files "manifest.json"> # AddType application/manifest+json json # </Files> AddType application/x-web-app-manifest+json webapp AddType text/cache-manifest appcache manifest # Video AddType video/mp4 f4v f4p m4v mp4 AddType video/ogg ogv AddType video/webm webm AddType video/x-flv flv # Web fonts AddType application/font-woff woff AddType application/font-woff2 woff2 AddType application/vnd.ms-fontobject eot # Browsers usually ignore the font media types and simply sniff # the bytes to figure out the font type. # http://mimesniff.spec.whatwg.org/#matching-a-font-type-pattern # Chrome however, shows a warning if any other media types are used # for the following two font types. AddType application/x-font-ttf ttc ttf AddType font/opentype otf AddType image/svg+xml svg svgz # Other AddType application/octet-stream safariextz AddType application/x-chrome-extension crx AddType application/x-opera-extension oex AddType application/x-xpinstall xpi AddType application/xml atom rdf rss xml AddType image/webp webp AddType image/x-icon cur ico AddType text/vtt vtt AddType text/x-component htc AddType text/x-vcard vcf </IfModule>
– reference: https://github.com/h5bp/html5-boilerplate/blob/master/dist/.htaccess
If you’re using a microsoft/IIS server please contact the server administrator and ask him to change the mime types for you.
Cheers!
PeterHey!
profil77- please update your theme to the latest version (Enfold 2.9.2) – maybe it’s an incompatibility issue with WP3.9.x or WP4.0. If the update doesn’t help please deactivate all plugins and check if this makes a difference.
Best regards,
PeterHey!
Please try to use ftp to update the theme: http://kriesi.at/documentation/enfold/portfolio-item/update-theme-files-with-ftp/
Regards,
PeterSeptember 6, 2014 at 11:39 am in reply to: SEO by Yoast Overriding the Facebook image problem #314455Hi!
I don’t know why facebook uses the logo. I check the source code and the og:meta and image tags contain the featured image of the product:
<!-- This site is optimized with the Yoast WordPress SEO plugin v1.5.6 - https://yoast.com/wordpress/plugins/seo/ --> <meta name="description" content="Beautiful large traditional dream catcher in black, brown and beige. The Feathers are real, not manufactured."/> <link rel="canonical" href="https://www.newageshop.com.au/product/traditional-dream-catcher-large-brown/" /> <link rel="publisher" href="https://plus.google.com/u/0/b/102179568412487160290/102179568412487160290/about"/> <meta property="og:locale" content="en_US" /> <meta property="og:type" content="article" /> <meta property="og:title" content="Traditional Dream Catcher Large Brown" /> <meta property="og:description" content="Beautiful large traditional dream catcher in black, brown and beige. The Feathers are real, not manufactured." /> <meta property="og:url" content="https://www.newageshop.com.au/product/traditional-dream-catcher-large-brown/" /> <meta property="og:site_name" content="The New Age Shop" /> <meta property="article:publisher" content="https://www.facebook.com/NewAgeShopOnline" /> <meta property="og:image" content="https://www.newageshop.com.au/wp-content/uploads/2014/06/product_036.jpg" /> <meta name="twitter:card" content="summary"/> <meta name="twitter:site" content="@NewAgeShopByron"/> <meta name="twitter:domain" content="The New Age Shop"/> <meta name="twitter:creator" content="@NewAgeShopByron"/> <meta itemprop="image" content="https://www.newageshop.com.au/wp-content/uploads/2014/06/product_036.jpg"> <!-- / Yoast WordPress SEO plugin. -->
The logo image itself is not set as og:meta image in the source code and it’s also not wrapped into a h1, etc. tag which might affect the facebook image parser. I recommend to contact the Yoast support team and to ask them why facebook doesn’t accept your featured image.
One reason could be the size of the images – facebook recommends too use images with a size of 600x600px or more: https://developers.facebook.com/docs/sharing/best-practices
Regards,
PeterHi!
Great, glad it works now :)
Regards,
PeterHi wmsgeorge!
Great, glad it works now.
Best regards,
Peter -
AuthorPosts