Sev

Same error for me

OK I found the issue, it was not related to WordPress version.
The issue comes from an incompatibility with the plugin “Caldera Forms”.
@oscomsupport Do you think you could investiguate the issue and provide an update of your plugin to solve this incompatibility ?

• This reply was modified 1 year, 1 month ago by Sev.

Thanks for 1.3.5, it solved the issue on my side.

Yes but even with a shortcode that looks like

[advanced_iframe securitykey=”9de1b189c3356de7880a3mykey”]

I can still view in the source of the page this thing :

<iframe id=’advanced_iframe’ name=’blabla’ src=’https://www.mywebsite.com/thisindex.html&#8217; width=’100%’ height=’1000′ scrolling=’no’ frameborder=’0′ border=’0′ allowtransparency=’true’ ></iframe>

And I would like to completly hide this hyperlink.

One solution could be to have a column in your big table that precise which role can read which row. Then you create different pages calling the table with direct filtering on this column (using the shortcode with filter). And then you manage the access to those different pages by “User Role Editor”.
The problem of that method is that if you want this information to be personalized, you have to create a page for each user.
Or else you could change the code of the plugin to force the filtering based on the user name (that WP can retrieve) => but each time Tobias will update his plugin you will have to update. I don’t think that you could manage this via custom templates which are independent from the plugin, but this could be the best way to stop displaying columns. I don’t know if you master Custom templates.

Perfect, that works !
And I also discovered a new way of working (in fact I should have read all your notes before….)
I will now make all my modifications to the custom template !
Thanks again for your precious help.

I am newbee regarding custom template… so I don’t even know where to edit that.
I looked into my template and used the editor to find any of the lines you were referring to but did not found any $this->the_record() or $this->the_field().

Could you give me the first steps ?

Finally I did a small function with a shortcode that allows me to select how many days I want to seek for birthdays. It is maybe not the simplest/fastest way to do it but it works :

function annif( $atts) {

extract( shortcode_atts( array(
		'how_many_days' => '7',
	), $atts ) );
require('./wp-load.php');
global $wpdb;
for ($i = 0; $i <= $how_many_days; $i++) {
    $day_shift = $i*24*60*60;
    for ($j = 18; $j <= 70; $j++) {
	    $past_day=mktime(0, 0, 0, date(n,time()), date(j,time()), date(Y,time())-$j)+$day_shift;
	    $results = $wpdb->get_results("SELECT last_name, first_name, date_birthday, private_id, responsible FROM wp_participants_database WHERE date_birthday=$past_day");

	    foreach ($results as $result) :
            $compteur = $compteur +1;
	    echo '<TR><TD align=right>', $j, ' ans : ', $result->first_name, ' </TD><TD><B>', $result->last_name, ' </B></TD><TD> <a href=sample-page/fiche-adherent?pid=', $result->private_id, ' target=_blank>', date(Y,$result->date_birthday), "/", date(m,$result->date_birthday), "/", date(d,$result->date_birthday), '</a></TD></TR> => ', $result->responsible, '<br/>';
        endforeach;
	}
}
}
add_shortcode('annif', 'annif');

Note that my variable $j seeks only for people from 18 to 70 years old as I don’t have younger or older.

Only suggestion/comment I have is my current way of working with “old” google chart :

function graph_women( $atts, $content = null ) {
   global $wpdb;
   $mens = $wpdb->get_var($wpdb->prepare( "SELECT COUNT(*) FROM wp_participants_database WHERE sexe = 'Man';" ));
   $womens = $wpdb->get_var($wpdb->prepare( "SELECT COUNT(*) FROM wp_participants_database WHERE sexe = 'Woman';" ));
   $per_mens = number_format(100 * $mens / ($mens + $womens),0);
   $per_womens = number_format(100 - $per_mens,0);

   /* https://code.google.com/intl/fr-FR/apis/chart/image/ */
   $data = '&chd=t:'.$per_mens.','.$per_womens.'';
   $colors = '&chco=6633FF,FF00FF'; /* if something, use &chco= */
   $size = '&chs=500x200';
   $bg = '&chf=ffffff';
   $title = 'Repartion Mens / Womens';
   $labels = '&chl=Mens '.$per_mens.'%|Womens '.$per_womens.'%';
   $advanced = '&chm=N*p0*,000000,0,-1,11'; /* don't work on pie */

   /*
   $charttype = 'lc';  /* line
   $charttype = 'lxy'; /* xyline
   $charttype = 'ls';  /* sparkline
   $charttype = 'gom'; /* meter
   $charttype = 's';   /* scatter
   $charttype = 'v';   /* venn
   $charttype = 'p';   /* pie2d */

   $charttype = 'p3';  /* pie */

   return '<img title="'.$title.'" src="https://chart.apis.google.com/chart?chtt='.$title.'&cht='.$charttype.''.$data.''.$colors.''.$size.''.$bg.''.$labels.''.$advanced.''.$title.'" alt="'.$title.'" />';
}

The concept is simple : use wpdb to set variables values then use the Google API.
But with your plugin, you write directly in the post the value of the variables, so that’s not so easy. Unless you know a method to send variables to a shortcode (that I don’t know).

Hello Ipagg,

I tested your plugin and it is very nice (I am currently using the “old” chart API, so I would like to transform all my graph to the new API).
I used the “old” API to have dynamic data in the graphs : I am sending queries to my wordpress database (I’m using Participant database) to be able to display percentage of men/women, etc.. which are real data and not a number entered as data.
Before digging in your plugin code, I would like to know if you expect to do such development on your plugin or not ?

Thanks
Bleu

I have another issue related to the frontend sort/filter.

In the “Manage database Fields” settings when you tick the “sortable” box, the field is well sortable in the “List participants” settings page.
But this is not reflected in the frontend sort nor in the frontend filter as in the frontend you have only access to the Main fields.

I would like to be able to do that. Do you think it will be changed in next upgrade or do I have to dig into the code ? May be the best flexibility will be achieved by defining the sort/filter fields (for example filter=’Name, birthday, city’)

The issue disappeared “magically”.
I try to better explain : somebody on computer A was performing a search on a page with your plugin, and somebody else on computer B when arriving on the same page was having by default the same search. It was very strange but now it disappeared so i will not investigate more on it ??

OK understood.
In fact it is the upload which cannot handle zero, again this CSV format !

The plugin manages well the zero, I just add to manually re-enter the missing zero that were not imported.

Hi again, there is something funny with the search and filter on frontend, it keeps the “memory” of the search, meaning that when you open a page on which somebody else did a search, you have what this person did search. What is not funny is that you cannot perform 2 searches/filters at the same time.
I guess you are storing the search and filter parameters in the database but this has a serious disadvantage ??

See you
Sev

Thanks for the 1.3.6, it solves this issue.