Traumflug

If one has public server space already, one can easily install a copy in a subdirectory. No need to buy more space. Database goes into a separate one or uses a different prefix (settable on one of the installer pages). For just testing, using public space is a good idea. Same hardware, same OS, same DB server, same PHP version. For development it's much better to have this stuff more accessible. Files directly editable, ability to install xdebug, to use custom tools, no fear to restart the server, such stuff.

While I can't fix it immediately: thanks for the report!

Das Multishop-Gedöns kann man auch später ändern. Auch wenn ein Multishop bzw. Multishops im Frontoffice wie getrennte Shops aussehen, intern und im Backoffice ist das nach wie vor ein einziger Shop. Die Funktionsweise ist relativ einfach. Da ist eine Logik, die sagt: "Wenn der Shop mit dieser Domain geladen wird, zeige Produkte dieser Kategorie(n), dieses Theme, etc. Wenn der Shop mit einer anderen Domain geladen wird, zeige die Produkte der anderen Kategorie(n), das andere Theme, etc." Will man nachträglich was ändern, muss man also nur die Produkte von einer Kategorie in eine andere schieben. Hat man Multishop eingeschaltet, erscheint im Backoffice auch ganz oben ein Menü in dem man auswählen kann, für welchen Shop (oder alle Shops) man die Einstellungen vornehmen will. Da muss man also immer aufpassen, dass man auch den gewünschten Shop bearbeitet. Einfach mal ausprobieren, ist nicht so sehr kompliziert. Learning by Doing war schon immer eine gute Idee.

Wo kann ich Informationen bekommen über Multi Shop & 30bs Funktioniert genauso wie bei PrestaShop 1.6, die Doku dafür ist also hilfreich. Mit welcher Version sollte man dies umsetzen. Es gibt nur eine Version von thirty bees. Ersten Schritte zum Multishop MultiShop einschalten. Backoffice -> Preferences -> General -> Enable Multishop. Dann erscheint unter Backoffice -> Advanced Parameters ein zusätzlicher Eintrag, mit dem man Shops anlegen und ihnen URLs zuweisen kann. Probiert man damit ein bisschen herum, erkennt man nach einer Weile eine gewisse Logik dahinter. Die 'Shop Groups' kann man wohl erst mal ignorieren und alles in eine solche Gruppe packen. ist es angedacht oder gibt es im Forum einen Abschnitt Erfahrungsaustausch mit anderen. Das ganze Forum dient dem Erfahrungsaustausch :-)

Well, saving a product kicks off like 15 Ajax requests, each of these tabs (Information, Prices, SEO, ...) is saved by a separate request, still all happens with a single click on the 'save' button. Looking at the code it looks much like earlier versions of PrestaShop saved tabs individually. This is faster, of course. If one changes something on one tab, then switches to another tab and clicks 'save' there, this change is lost, though.

I looked in my transformer theme header.tpl and searched for “Always Paws” but it isn’t found and I don’t see where to change it. Watch out for $shop_name. You can replace something like title="{$shop_name|escape:'html':'UTF-8'}" with title="My awesome dog shop"

Hah, a visible message :-) For the records: @DVD could/can see all his messages.

Tried to contact him by email and got an automated response from a support system.

Hmm. Again an empty reply.

My /img folder grow so big. I think there are a lot of unused images. Regenerating thumbnails should fix this. Slower, of course, because all used pictures get resized again, but available without module.

Uhm. Glancing over this discussion quickly I think nobody recommended to regenerate thumbnails so far. While it's named 'thumbnail', it actually means all displayed pictures. Backoffice -> Preferences -> Images, bottom of the page. Regarding storage location, product images are in img/p/, inside there are numbered folders, at the bottom one folder per product, with images in 10(!) sizes inside (by default).

Could you not just tell the customer in advance what payment methods you accept? In Europe that's actually mandatory and the default thirty bees theme already does this by showing a picture with payment logos on the product page.

Never seen an online shop offering/asking for a tip. Nevertheless, product customizations could do the trick. One would add a number of predefined tips (e.g. $1, $2, $5, $10) as a product customization, along with the respective price impact. Another way would be to make such a tip a separate product, then list them as recommended products.

Nice work! Assuming by the name, it's the original beesblog module with fixes applied. How about making pull requests with these changes to get them into upstream, into the original module? This way a lot more people can appreciate your work, as it automatically appears in their backoffice then.

It's apparently a problem with the Jmspagebuilder module. Disabling that should make the error go away. If you need the module, its developer should be able to help.

@MockoB I’m talking about design without any functionality modifications. You asked for performance improvements. This does mean functionality modifications, even if the resulting behavior is the same. There is no magic "make it faster" button a developer can click, such code usually has to be rewritten from scratch. Thus I agree with the other responders: it's better to choose an already well performing template and build upon that. Changing colors and rearranging a couple of design blocks is much easier and can indeed be done in the 4-digit price range.

Rewriting a whole template? Depends on the feature count/complexity, of course, but a first guess would be half a year of fulltime work = some 50'000 Euros. This also assumes these nice features can actually be implemented in a better performing way. Maybe this very rough estimate answers your question already.

@RandomFish We have tried to redo our site in 1.7, 1.7.1, and 1.7.2. Its not working. It is the absolute worst piece of software from a developer and merchant stand point I have seen. It does look nice, but nothing works. Nothing at all. Taxes. Rounding. Random errors that appear to go away. It is a software abortion. Well, this kind of observation is pretty much the reason why thirty bees was founded. PS 1.7 has some good ideas (like moving logic out of templates, into PHP) and some not so good ideas (like partially moving to Symphony), but all this stuff is of not much help if the outcome isn't usable. Welcome to thirty bees, @RandomFish !

it needs to be able to update the price every time something is selected in the set by the customer. Product combinations can actually do this. It's named "impact on price" The only things I consider to be missing is: Make combinations from existing products, one has to enter these combinations in addition to the single product. Price impact has to be done manually, too. Probably needed with Magento as well, because I'd take that price impact on a combined product usually doesn't exactly match the price of the separate product. E.g., adding a $10 SD card to a $80 camera doesn't end up in a $90 combination (like Magento would do it), but gets priced $89. Looks like it largely depends on how often you want such combined products. Also whether you actually intend to sell the combination add-ons separately. To find out how well it works, one can only try. I think it's worth such a try.

As this is probably a larger thing I've opened a Github issue for it: https://github.com/thirtybees/community-theme-default/issues/27

This error means that there's no matching language pack on the thirty bees server. Still the installation should finish with English only. Does it?

@Occam A developer named gabdara posted a commit on Github last Friday. Thanks. I just applied this patch to 30bz and pushed it to a new branch import. Totally untested, it might even contain syntax errors. For your convenience and if you don't run off a Git clone, here's the patched file (replace the one in controllers/admin/): 01503312519447AdminImportController.php Let us know how it works :-)

Screenshots, please! We want to see what you see :-)

@yaniv14 And I was unable to install the bees blog That's pretty vague. I see you committing code from time to time (thank you very much!), so I'm pretty sure you could do a first few steps into debugging this issue. For example, like equipping those failures you experience with proper error messages. And then creating a reproducible test case? That'd be nice and helpful.

AFAIK, these downloadable files on Github are auto-generated, so developers have no influence on how they're named. One of the many oddities of Github.