tbirnseth

Thx for the correction Ecom.  Was working from memory (not always the best) and use the data-no-defer very infrequently (like maybe once in the 5 years it's been around!).

There's no conflict between "Marketplace" and "Multi-Vendor".  I think you're trying to solve a problem that doesn't exist.

Can I then state that the API documentation is incomplete in some cases?

Thanks for the morning chuckle!

Can I then state that the API documentation is incomplete in some cases?

Don't want separate product_id's for simple options.  This isn't Tee Shirts. It's not an inventoried item.  

Variations also don't solve the problem of being able to provide a template that the data is editable by the vendor but the template is managed by the site admin.  And (as I understand it) variations use Features, not Options.

Guess I'll have to write an addon to get the prior 'option template' type functionality back. 

This removing valid features because you want to force people to conduct business in some one-size fits all approach is really poor software/business plan.

it was giving error 

why didn't you address the error?  You really can't expect us to help you when you don't provide full and complete information.  If you are not a developer and can't address an error in untested code, then I'd strongly suggest you hire someone who can.

Does that mean the entry will then be rewritten (based on the entries in add_on.xml)? 

So far, I haven't dared to delete the entry, just edited it (in the cscart_addons table).

Can I actually delete it?

 

If you remove or rename it, the addon is effectively uninstalled.  I made this suggestion ONLY because I though you deleted the files BEFORE uninstalling the addon.  Hence there's no way to find the data to uninstall.

Rather than using src="https://example.com/image.png"use src="//example.com/image.png" instead.  It will use whatever the current protocol is that's in the current state.

All images are in images/detailed/*

Thumbnails are generated from those images and cached in images/thumbnails/[width]/[height]/*

so if you know the dimensions of the image you can retrieve them from the appropriate directory.  You don't need the api to do this.

I believe Ecom's point is that updates may not be moderated and hence an initial value may not be a problem, an update could be.  

I don't know specifically what's enabled in the various MVE variant products.  I was just offering it as a possiblity.  But contacting helpdesk is the best solution.

Of course, if you know specifically which you want enabled, a small amount of custom work could enable it for you.

I explained in in #2 above.  It is not a 'link', it is a page within the controller (addon) based on the 'mode' passed to the controller.  Just go look at other addons that have multiple 'modes'.

Just google "cs-cart developer documentation"

You only need to escape the class when it is nested inside another file that has a 'use' clause that conflicts with the base classes.  So if you find that it's looking for the Tygh class inside of another class, use the escape.

Try using: 

$event_dispatcher = \Tygh::$app['event.dispatcher'];

Have you read the developer documentation?

Basically every "mode" of a controller (addon) can have a corresponding template file that is loaded when the controller completes.

Most common template files that map to modes are:

+ manage

+ update

+ edit

+ import

+ etc

Hence a ?dispatch=my_addon.edit&id=123 would first execute app/addons/my_addon/controllers/backend/my_addon.php

It would act on the $mode, setting template variables, validating security, etc.

When my_addon.php returns, then design/backend/addons/my_addon/views/my_addon/edit.tpl would be loaded with the template variables set from my_addon.php.

For details, read the documentation. 

I'd suggest you create a variation that was for 'carton' where the quantity is 12 and the step is 12.