Plugin Support
Gabor
(@nextendweb_gabor)
Hi @cpickhardt!
I’m sorry, but we don’t have such an option. The importing has to process too many codes (more than exporting), and PHP limitations would be easily reached, if we would allow multiple sliders to be imported together. So you are only able to import sliders one-by-one, to avoid errors.
Thank you for your timely response! I appreciate it!
Are you able to tell me if the .ss3 files that we get via export are able to be found anywhere within the plugin’s file structure? So we would be able to grab all of the files and just port them over to another server? Or do we need to get them ONLY via the export function?
Plugin Support
Laszlo
(@laszloszalvak)
Hi @cpickhardt
The .ss3 file is basically a compressed file that contains:
- the structured data of the slider and its slides
- and a group of attachments
that we collected from the database and the file system for export. On its own the .ss3 file can not be used for anything, as it is our import flow that processes it and restores that data as a slider.
So I am sorry, but you can not simply copy them from one place to the other, unless you migrate the website itself ( with the database and the files ).
Tip: if you have developer experience, then you could also use the Public PHP API of Smart Slider 3:
to import .ss3 files to your website.
Best regards,
Laszlo.
Hi there Laszlo, thank you! I do have developer experience, so I will look into this, but just to confirm, even using the API we would have to import sliders one by one, is that correct?
Plugin Support
Laszlo
(@laszloszalvak)
Hi @cpickhardt
Well, you can try running the PHP method in a “for” loop, but if you reach server limitations -eg.: memory limit being reached -, then yes, you should try it rather with smaller groups or one by one.
Hey there,
Would I put that import line inside of my functions or hooks file, or would I need to do it directly in the plugin’s files? (This seems counterintuitive, I just want to make sure I am reading the documentation correctly).
And also, am I able to change the “Temp” directory that the non-local import calls from by providing another path, or no?
Plugin Support
Laszlo
(@laszloszalvak)
@cpickhardt
The purpose of that PHP code is to import an .ss3 file from that path that you specified in its 1st parameter, so you can enter there any valid path until the .ss3 file exists there.
Where to run the code:
You can put this code to anywhere, so e.g. your theme, or a custom plugin, all that matters is that, you probably don’t want to run this code each time somebody visits your site, as that way you will import multiple times. So I would suggest you to wrap it with a condition, so e.g. it runs only when you visit a specific page, or when a specific GET parameter is set.
However please note that, custom coding is out of the scope of our support, so although I gave a couple of suggestions, we are unable to provide support for these coding queries, I am sorry.
Best regards,
Laszlo.
Thank you so much for this, Laszlo!
I’ve started imports and I only have ONE final question, I promise. Are we able to change the IDs of sliders that we have? Some of our sliders that we are importing are not importing with their same IDs from our old site (which, of course, makes sense) but it would be great if we could make them match, so that we don’t have to alter the shortcodes in our pages/posts. Totally fine if not! Just figured I would ask 🙂
Plugin Support
Laszlo
(@laszloszalvak)
Hi @cpickhardt
I am sorry, but our API doesn’t have an option for that, as the main purpose of this API is rather to give developers an option to create default or sample sliders for their clients. The “Restore slider” logic you are looking for:
is available only during the normal import flow in form of an user controlled setting, as that will also delete the existing slider if there was one with the same ID and there is no way of recovering the original slider.
As I mentioned above, custom coding is out of the scope of our support, and we never suggest modifying core files, but temporarily until you finish the importing you could modify our Project.php file:
- \wp-content\plugins\smart-slider-3\Nextend\SmartSlider3\PublicApi\Project.php
so you enable the replacing logic on the “ImportSlider” instance by calling its enableReplace() method, e.g.:
...
$import = new ImportSlider($applicationType);
$import->enableReplace();
...
then you could start the importing via your custom code and that will always import the slider back with the original ID ( and also delete any existing slider with the same ID ).
Once you are done, don’t forget to revert the Project.php file back to its original code.
Best regards,
Laszlo.
