I am building a site that takes public user registrations, and logged in users will be able to manage their profile, and redeem coupons from products they purchased.
Coming from a Wordpress background I will probably be doing this with plugins like Contact Form.
With Drupal 8, do you suggest to do this with the core user registration functions, or with the WebForm module?
This project was for a leading real estate company with a broad customer base throughout the world. The company is currently developing projects that are estimated to cover more than 89.7 million square feet.
Hello, I've made an e-commerce website with Drupal Commerce, used Composer to install core and modules. I now have to migrate it to client's server which does not have composer.
How should I proceed to upload the website to the server? I can only have an FTP account and DB access. I won't be able to install composer on the server.
Hello, I‘ve a drupal installation with user registration. The user can edit some values and store a „blob“ file. Now comes the tricky part, i want to build an „electron desktop app“ (electron in short = browser view). This app should show an „login in“, after the “login in”, the big file, and some values from the database should downloaded to the users client. Every user has it‘s own file. After Edit there should be a „one click upload solution“.
Hello community, maybe someone can help me here, or give me at least an advice how i can solve this problem.
I‘ve a drupal installation with user registration. The user can edit some values and store a „blob“ file. Now comes the tricky part, i want to build an „electron desktop app“ (electron in short = browser view). This app should show an „login in“, after the “login in”, the big file, and some values from the database should downloaded to the users client. Every user has it‘s own file. After Edit there should be a „one click upload solution“.
We ran our site on security tool Burp Suite and got below message/issue:
The URL path filename appears to be vulnerable to XML injection. The payload ]]>>< was appended to the value of the URL path filename. The application's response indicated that this input may have caused an error within a server-side XML or SOAP parser, suggesting that the input has been inserted into an XML document or SOAP message without proper sanitization.