madn3ss75

Ops, 1.4 compatibility was not one of my goals. I’m sorry.

Regarding the hooks, they are different from the (customizable) header and footer template files.
I’m not so good at prestashop (maybe due to lack of documentation), but I believe that you could render a single template file using some simple methods from the FrontController (such as setTemplate() and display()).

Thanks.

Giuseppe

Ok, maybe i’m starting to understand.
Did you changed the way to match a keyword phrase against the page sections?
I mean, now your are matching a phrase like if it is written between double quotes in google. Right?
A few time ago it was matching like if there’s no double quotes, so all the parts of the keyword phrase can be matched inside the sections independently.
That is (in my opinion) the same behaviour that google has while indexing.

Ok. What is the meaning of the ajax dropdown keywords list that appears when you start to write in the focus field?

I’m sorry, but I don’t think so.
The functionality of the focus field was ok before one of the latest release.

It’s common that more than one keyword are used to test if all of them are matching in all the sections of the page (title, url, meta description, etc…).
At least I’ve used it like so until now. Maybe i’m doing wrong, but I’ve experienced satisfactory results with google.

P.S: Sorry for the “Nonsense”, I didn’t mean to use it like an insult. ?? I’m italian, my english is not so good.

Same problem here, it seems a bug that was introduced with one of the latest updates, maybe a week ago or something similar.

The functionality of this tool was perfect before.
The tool seems to search the keywords inside article/url/title/meta that have a perfect match with the one written in the focus field.

For example.
Title: Iphone, Android… which one?
URL: iphone-android-which-one
Meta: Choosing from Iphone and Android is a….

In the focus field: iphone android –> gives 1 Yes (URL)
In the focus field: iphone, android –> gives 1 Yes (Title)
In the focus field: iphone –> gives 5 Yes

In the Preview Snippet the keywords are highlighted correctly…

This is a nonsense. Someone has a solution or a workaround?

I found the problem.
You need to add at line 71, just before
$templates = array_merge($templates, self::add_template_set($template_prefix));
the following code:
if (!empty($template_prefix))

And the problem is gone.

You need another thing:
– find

// Scripts
				wp_enqueue_script( 'simplemap-master-js', site_url() . '/?simplemap-master-js', array( 'jquery' ) );

-replace with

// Scripts
				wp_enqueue_script( 'simplemap-master-js', site_url() . '/'.qtrans_getLanguage(). '/?simplemap-master-js', array( 'jquery' ) );

This thing is evolving, but for the moment it seems to work properly.
Cheers.
Giuseppe

If you edit a little bit of code you can resolve the issue quite eaily.
Open simplemap/classes/simplemap.php
Find the load_plugin_textdomain() call and delete it.
Insted put an “init” call:
add_action('init', array( &$this, 'init_plugin_lang'));
Outside the function Simple_Map() declare this function:

function init_plugin_lang(){
      $plugin_dir = basename( SIMPLEMAP_PATH );
      load_plugin_textdomain( $this->plugin_domain, 'wp-content/plugins/' . $plugin_dir . '/lang', $plugin_dir . '/lang' );
    }

Here you are. Your SimpleMap plugin is working togetherwith qTranslate.
Remember to setup the .mo files for your language inside the /lang folder of the plugin.
And don’t forget that an (*eventual*) update to the plugin will blow up all of your edits, so pay attention when updating and backup your code before.

Cheers.
Giuseppe