this.menu = new Ext.menu.Menu({
items: [{
text: 'Anmeldung',
icon: 'open_in_new',
handler: function () {
window.open(`(...)`, `_blank`)
}
}],
cls: 'pimcore_navigation_flyout'
})
Hello guys,
Can anyone help my customer save function is not working
can anyone tell whats wrong i been stuck
public function addAction(
Request $request,
CustomerProviderInterface $customerProvider){
if (0 === strpos($request->headers->get('Content-Type'), 'application/json')) {
$data = json_decode($request->getContent());
}
\Pimcore\Model\Version::disable();
$customer = $customerProvider->create();
$data->profiling=true;
$data->oAuthKey=false;
$customer->setActive(true);
$customer->setFirstname($data->firstName);
$customer->setLastname($data->lastName);
$customer->setEmail($data->email);
$customer->setStreet('street');
$customer->setZip('361005');
$customer->setCity('jamnagar');
$customer->setGender('male');
$customer->setPassword('1234567890');
$customer->setCustomerLanguage($request->getLocale());
//$customer->setParentId(54);
$customer->setPublished(true);
$customer->setCountryCode('IN');
//$customer->setProfiling($data->profiling);
$customer->saveDirty(false);
try {
//check if special redirect is necessary
//$response = $this->redirectToRoute('account-index');
return $this->json(["success" => true, "data" => $customer,'response'=>"success"]);
}
catch (\Exception $e) {
$errors = $e->getMessage();
}
return $this->json(["success" => false, "data" => $errors]);
}
Status: 500 | Internal Server Error
URL: /admin/email/send-test-email
Method: post
Message: Call to a member function send() on null
Trace:
in /var/www/html/vendor/pimcore/pimcore/lib/Mail.php:572
#0 /var/www/html/vendor/pimcore/pimcore/lib/Mail.php(505): Pimcore\Mail->sendWithoutRendering(NULL)
#1 /var/www/html/vendor/pimcore/pimcore/bundles/AdminBundle/Controller/Admin/EmailController.php(433): Pimcore\Mail->send()
#2 /var/www/html/vendor/symfony/http-kernel/HttpKernel.php(156): Pimcore\Bundle\AdminBundle\Controller\Admin\EmailController->sendTestEmailAction(Object(Symfony\Component\HttpFoundation\Request))
#3 /var/www/html/vendor/symfony/http-kernel/HttpKernel.php(78): Symfony\Component\HttpKernel\HttpKernel->handleRaw(Object(Symfony\Component\HttpFoundation\Request), 1)
#4 /var/www/html/vendor/symfony/http-kernel/Kernel.php(199): Symfony\Component\HttpKernel\HttpKernel->handle(Object(Symfony\Component\HttpFoundation\Request), 1, true)
#5 /var/www/html/public/index.php(36): Symfony\Component\HttpKernel\Kernel->handle(Object(Symfony\Component\HttpFoundation\Request))
#6 {main}
Hey guys, quick question regarding a templating issue I am running into (Pimcore X):
I have several AreaBricks, ie: Content, Header and an usp, all these Areabricks have a common editable with the name title . This is no issue when using the pimcore_areablock function.
However, when I Include these areabricks in a 'fixed' setup, the blocks individually load, but together give an error that the title editable is a duplicate, Which makes sense.
The template has multiple instances of the content brick which means that a simple rename in the content brick to a 'per-brick' unique editable name would not work:
Header : title
Content : title
usp : title
Content 2 : title
Content 3 : title
Header : header-title
Content : content-title
usp : usp-title
Content 2 : content-title
Content 3 : content-title
Is there a way for fix this without renaming the editables? Am I perhaps missing something? Thanks in advance!
good morning!
I want to achieve the following:
(pimcoreX and coreshop 3)
There are different products like TShirts and Shoes, all with different attributes.
Each variant of a product (ie Tshirt blue in XL or black in S) results in another product-price.
You could say - each variant is a product-option with a price. Options combined (blue with XL | black with S) result in a different product-price.
each product-type (TShirt|Shoes) could have more than 1 attribute defined as variant/option.
I need the possibility to define for each option/variant a unique product-price.
Where and how to set the price-definiton for the variant? So that coreshop could recognize/calculate it?
In an objectbrick - I cannot put a storeValue (price) for it as separate attribute.
Is it better to define variants - or are options a better way?
How to define theese options?
Did you have/had any similar definitions needed in pimcore/coreshop? How did you solve it?
In coreshop 2-doc I see something like:
https://docs.coreshop.org/2.1.0/Development/Products/Multiple_Product_DataObjects.html
but there are no product options/variants with different prices
Any help appreciated