Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • December 28, 2016 at 10:47 am #728350
    Elmar
    Guest

    Hey there,

    it is impossible to reply to requests from your support staff because the forum is closed. Let me know how to change that. We are a business and this not a hobby so we rely on a fast response.

    Thanks and appreciated,
    Elmar

    December 28, 2016 at 12:52 pm #728355
    Yigit

    Hey Elmar!

    It seems to work fine on my end. I attached screenshots in private content field. I noticed that you mentioned update was 3.8. Currently the latest version is 3.8.4. Can you please firstly update Enfold to the latest version – http://kriesi.at/documentation/enfold/updating-your-theme-files/ on stating site and check if issue remains?

    Also, please note that this is not just a hobby for us either. However, this is the only holiday we have. It boosted our performance in the past and i am pretty sure it will in future as well :)

    Cheers!
    Yigit

    December 28, 2016 at 4:34 pm #728365
    El

    Hey Yigit,

    I am all for a holiday. It is just frustrating to not be able to reply on a thread when someone needs a reply from your staff. I completely understand that you close it for new requests.

    Sorry for the staging site not being updated. I pulled a new image from live and forgot about it. I just updated ONLY the theme. Now you can see what I meant.

    It would be great if you could change this behaviour or at least make it configurable so that portfolio is able to be based on root instead of the blog link.

    Best,
    Elmar

    December 28, 2016 at 5:21 pm #728372
    Yigit

    Hi,

    I added following code to functions.php file of your child theme

    add_filter('avf_portfolio_cpt_args','av_change_portfolio_slug');
function av_change_portfolio_slug($args){
    	global $avia_config;
 
	$labels = array(
		'name' => _x('Portfolio Items', 'post type general name','avia_framework'),
		'singular_name' => _x('Portfolio Entry', 'post type singular name','avia_framework'),
		'add_new' => _x('Add New', 'portfolio','avia_framework'),
		'add_new_item' => __('Add New Portfolio Entry','avia_framework'),
		'edit_item' => __('Edit Portfolio Entry','avia_framework'),
		'new_item' => __('New Portfolio Entry','avia_framework'),
		'view_item' => __('View Portfolio Entry','avia_framework'),
		'search_items' => __('Search Portfolio Entries','avia_framework'),
		'not_found' =>  __('No Portfolio Entries found','avia_framework'),
		'not_found_in_trash' => __('No Portfolio Entries found in Trash','avia_framework'),
		'parent_item_colon' => ''
	);
    $permalinks = get_option('avia_permalink_settings');
    if(!$permalinks) $permalinks = array();    

    $permalinks['portfolio_permalink_base'] = empty($permalinks['portfolio_permalink_base']) ? __('portfolio-item', 'avia_framework') : $permalinks['portfolio_permalink_base'];
    $permalinks['portfolio_entries_taxonomy_base'] = empty($permalinks['portfolio_entries_taxonomy_base']) ? __('portfolio_entries', 'avia_framework') : $permalinks['portfolio_entries_taxonomy_base'];
	$args = array(
		'labels' => $labels,
		'public' => true,
		'show_ui' => true,
		'capability_type' => 'post',
		'hierarchical' => false,
		'rewrite' => array('slug'=>_x($permalinks['portfolio_permalink_base'],'URL slug','avia_framework'), 'with_front'=>false),
		'query_var' => true,
		'show_in_nav_menus'=> true,
		'taxonomies' => array('post_tag'),
		'supports' => array('title','thumbnail','excerpt','editor','comments'),
		'menu_icon' => 'dashicons-images-alt2'
	);
return $args;
}

    and then flushed permalink settings. Please review your website now :)

    Best regards,
    Yigit

    December 28, 2016 at 5:44 pm #728378
    El

    Sweet Jesus, Christmas came late this year. I still suggest that you implement this as a standard or at least as an option that can be checked. Separating the blog posts from the actual pages is a defacto standard for every non-Blogger site.

    Thanks for the quick fix, Yigit.

    Now I am stretching my luck but I´ll give it a try nonetheless and pester you with the other open ticket. Another team member answered to this request but I am unable to reply:

    Order now button disable after click or/and show message

    I already did all this but the forward action “order now” still takes ages to complete and there is no visual hint that the server is processing the request. I would recommend to deactivate the button and have a message like “Processing…” or an ajax loading sign or whatever in order to indicate that something is actually happening.

    Enjoy your holiday… as much as you can ;-).

    Best,
    Elmar

    December 28, 2016 at 7:35 pm #728383
    Yigit

    Hi Elmar,

    I added following code to bottom of Style.css file of your child theme on your staging site

    .blockUI.blockOverlay:after { content: "Processing…"; font-size: 40px; color: red; width: 100%; position: absolute; bottom: -20px;  }

    Please add it to your live site and adjust it as needed :)

    Best regards,
    Yigit

    December 28, 2016 at 8:35 pm #728390
    El

    Yigit, thank you very much. That was outstanding support, man!

    Have a great 2017,
    Elmar

    December 29, 2016 at 2:23 am #728395
    Ismael

    Hi,

    Great! Let us know if you need anything else. See you on 2017! :)

    Best regards,
    Ismael

  • Author
    Posts
Viewing 8 posts - 1 through 8 (of 8 total)
  • The topic ‘Support questions from staff cannot be answered’ is closed to new replies.