ongr-archive / oxidconnectorbundle Goto Github PK
View Code? Open in Web Editor NEWDEPRECATED, DO NOT USE WILL BE REMOVED
License: MIT License
DEPRECATED, DO NOT USE WILL BE REMOVED
License: MIT License
Despite the name talks for itself, I think only installation guide is not enough. IMO at least one sentence about what this bundle does would be nice for introduction.
Test whole process:
Currently when importing from OXID, no urls are set for product/category/content documents.
Connector should import custom SEO urls or generate them using rules from http://wiki.oxidforge.org/Tutorials/Understanding_OXID_SEO
Relation definitions needs updating:
Seems like most of things defined here are not used anywhere
ongr_oxid:
database_mapping:
oxid:
tags:
@shop_tag: '_1'
@lang_tag: '_1_en'
shop_id: 0
lang_id: 0
entity_namespace: ONGROXIDConnectorBundle
In installation guide "oxid" es manager is used, but not fully documented its configuration. Should be documented fully or changed to default manager, to make installation easier.
We need to analyze if we can set up multilanguage shops in oxid connector and write documentation for it.
There should be default pipelines configured in connector, for easer launch out of the box.
Review composer.json and update to support newest bundle versions.
https://github.com/ongr-io/OXIDConnectorBundle/blame/master/Resources/docs/index.rst#L8
At current time there is no stable version of bundle, those documentation should be changed or stable version should be released.
hi,
i am followed the bundle with the purpose to see other connections to oxid than my own, that we created the last weeks. So i wanted to have a look into the migration. At the first view the mapping on the database cols seems to be very cool and easy, but it isn't oxid has got a lot of logic in their objects, that manipulates them. So you can't see the database tables as the entities you can work with. I will give you two examples:
You won't ever see the value of OXPRICE
in the frontend. The value is manipulated depending on several shop settings (net/brut view, payment rules)
Your mapping will work for shops with one base language. Oxid generates the translations by adding an extra col to the database table like title_1
, title_2
, ... So you won't be able to map the right col in your entity for the migration.
I would see two different solutions. Both base on the situation, that you need Oxid the oxid logic (means the shop it self) in between.
oxArticle
's save()/delete()
method and create their own mapping to the document you persist. Mostly the devs would same methods/mechanism that oxid is calling when creating the values for the frontend.Even when i would mean to create an other package/module, i would prefere the first solution.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.