This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.
Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.
Hoy no hay técnicos de soporte disponibles en el foro Juego de herramientas. Siéntase libre de enviar sus tiques y les daremos trámite tan pronto como estemos disponibles en línea. Gracias por su comprensión.
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
|---|---|---|---|---|---|---|
| - | 7:00 – 14:00 | 7:00 – 14:00 | 7:00 – 14:00 | 7:00 – 14:00 | 7:00 – 14:00 | - |
| - | 15:00 – 16:00 | 15:00 – 16:00 | 15:00 – 16:00 | 15:00 – 16:00 | 15:00 – 16:00 | - |
Supporter timezone: Europe/London (GMT+00:00)
Este tema contiene 34 respuestas, tiene 4 mensajes.
Última actualización por hace 6 años, 2 meses.
Asistido por: Nigel.
I was waiting for the Types update so we don't have to worry about whether the patch has been applied properly, but the queue for testing CRED and Views has taken longer than expected, and Types QA testing is only beginning now, so won't be out before next week.
I just checked again and it is working fine on my local copy of your site (screenshot).
Hostal Bumba opened 14 minutes ago, and you can see the horario post that corresponds to today.
If your live site shows "Cerrado*" then you can see from the shortcode that that is a catch-all in case the other conditions were not met.
add_shortcode( 'abierto', function(){
global $post;
// get UTC offset for current WP timezone
$offset = get_option('gmt_offset');
$now = date( "H", time() + $offset * 60 * 60 ); // current locale hour in 24H format
// get horario posts related to current alojamiento
$horarios = toolset_get_related_posts(
$post->ID, // current post
'alojamiento-horario', // relationship slug
'parent', // current post is parent of horario
1, // limit to single result
0, // offset
array( // get the horario post for today
'meta_key' => 'wpcf-dias-de-la-semana',
'meta_value' => date( "N", time() + $offset * 60 * 60 ),
'compare' => '='
),
'post_id', // return post id
'child' // role to return
);
$estado = get_post_meta( $horarios[0], 'wpcf-estado-de-apertura', true );
if ( $estado == 2 ) {
return "Cerrado";
}
$jornada = get_post_meta( $horarios[0], 'wpcf-jornada', true );
if ( $jornada == 1 ) {
$apertura = get_post_meta( $horarios[0], 'wpcf-hora-de-apertura', true );
$cierre = get_post_meta( $horarios[0], 'wpcf-hora-de-cierre', true );
if ( $now >= $apertura && $now < $cierre ) {
return "Abierto!";
} else {
return "Cerrado";
}
} elseif ( $jornada == 2 ) {
$apertura1 = get_post_meta( $horarios[0], 'wpcf-hora-de-apertura-de-la-manana', true );
$cierre1 = get_post_meta( $horarios[0], 'wpcf-hora-de-cierre-de-la-manana', true );
$apertura2 = get_post_meta( $horarios[0], 'wpcf-hora-de-apertura-de-la-tarde', true );
$cierre2 = get_post_meta( $horarios[0], 'wpcf-hora-de-cierre-de-la-tarde', true );
if ( ( $now >= $apertura1 && $now < $cierre1 ) || ( $now >= $apertura2 && $now < $cierre2 ) ) {
return "Abierto!";
} else {
return "Cerrado";
}
}
// catch all
return "Cerrado*";
});
That suggests that $jornada is neither 1 nor 2, which is where to start looking if something is going wrong.
I would add some messages to echo the variables such as $jornada to the error log as they are created which should enable you to identify when something is unexpected and hopefully see why.
