Resolved Error 1064 new install with joomla 3.3.6 and vm 3

Hello,

I did a new install on a domain but I get this error:
1064 You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near '' at line 3 SQL=SELECT name FROM hxtz4_csvi_template_settings WHERE id =

I reinstalled a couple of times, fixed database ect. But I don't know to solve it.

I have installed
3.3.6 joomla
3.0 virtuemart
5.19 csvi pro

Perhaps you have an idea?

Hello,

I have merged your 2 topics, just so they are together.

When do you get this error? After you selected a template from the dropdown and click on Open? When you click Import or Export? Explain me a little bit more of the process that leads up to this error.

The main issue is that something gets started but there is no template ID.

P.s. Interesting to see you have it running on MariaDB

Thx for replying,

It happening when I select import - virtuemart - product import
I select the csv file, click on process

Than the error shows up, no debug file.

That explains it, there is no template.

After you selec the import - virtuemart - product import you need to click on Go. So the settings for this import are loaded. After that click on Save As to save your settings into a template.

Any further imports you can select the template from the dropdown and open it by clicking Open.

After that select the file you want to import and click Process.

Try that and see how it goes.

that was not very smart by me
Done that, I get no errors but a processing.

It is a almost blank page, there a 3 blinking rectangular shaped things for more than 10 min now.
with some other text like what template that is importing

That is 1 step further

If you are importing a small file it shouldn't take that long. Have a look at this page, Using Firebug to analyze import problems, and let me know what you find. It may also be a plugin that is messing with the import requests. Let's see what you find.

I get the following error is firebug:

SyntaxError: identifier starts immediately after numeric literal

That means nothing to me. Can you post a screenshot of the Firebug view where this error is shown? Just to get an idea what is generating this error. If you can make screenshots of all the tabs (Params, Headers, Response) that will be useful.

Now we know that something is preventing CSVI from running the import.

sry for the late screenshot.
[img size=400]http://kerckhoeve.org/images/screen_1.PNG[/img]

If you need more, I'll hear it.

Hello,

The screenshot is not attached. Can you try again? If it is too big, try zipping it before uploading.

sry the server is down where the image is on.

There is apparantly something odd with the code. What is the name of your template?

On the screenshot where you see the error, there is a filename and line number at the end in blue. Click on that and please post a screenshot of what shows up then. That should highlight the problem.

Here is the screenshot,

[img size=400]http://kerckhoeve.org/images/screen_2.PNG[/img]

[img size=400]http://kerckhoeve.org/images/screen_3.PNG[/img]

I have beez selected as template.
But I have instyle installed from gavick.com

oke I found it, max_execution_time was set on 128M
What is strange because M are no seconds.

but another error

[img size=400]http://kerckhoeve.org/images/screen_4.PNG[/img]

oke I found it, max_execution_time was set on 128M

That is strange, almost looks like someone tried to set the memory level to 128M but instead changed the maximum execution time.

but another error

The real error here is not the JavaScript about the progressbar but the SQL query you see. This has to do with the data being imported.

Please start a new topic stating that you have a problem importing custom fields and post all the requested information from the top especially the debug log. Since you get this error you may need to find the debug log manually in the folder tmp/com_csvi/debug and then the last file.

A quick thing you can check is to see if your custom field names are correct in the import file.