partitioning – is it possible to use a SATA DOM drive as a recovery boot device, while using the SATA DOM to host recovery VM OVA files?

For some background, I have loaded oVirt (similar to CentOS) v4.2.2 on a SuperMicro server. The server is using a RAID10 on 4TB 2TB drives, however the important part has to do with the SuperMicro SSD (DOM SATA). I can make this SATA DOM a recovery boot drive for the operating system using the command:

dd if= of=/dev/sde

where / dev / sde is the device path for the SATA DOM. While I can make this a boot drive, I was wondering if there was also a way to include OVA files in the SATA DOM, which could be mounted on the server and copied to import virtual machines in a recovery case. I've tried creating multiple partitions, which makes the device no longer bootable, and I've tried mounting the boot SATA DOM on the server and then adding the OVA files, but since the SATA DOM is converted to an ISO9660 file system After copying over the oVirt ISO, it is not read / write mountable. Any help is appreciated. You will be happy to attach / etc / fstab, lsblk, / dev / mapper /, etc.

javascript – Modifying DOM CSS using JS – What is the correct syntax?

So, I have a code below that works well:


            Javascript practice 




I have many comments that say that when I access the DOM-style property, I need to set the value as strings, such as setting not to a number like I've done here, but to add w + "px"

I am baffled because I am using Brackets as a code editor and I am implementing it in Chrome. My code works fine and every time I load the HTML page, it initializes a div of the required dimensions. Everyone tells me that it will not work, which is what confuses me.


magento2 – Magento Framework Config Dom ValidationException: Element & # 39; argument & # 39 ;: Duplicate key sequence

I have an error when developer mode is active.
The exception is dropped when entering any product detail page.
I am running magento 2.3.4
Could you help me find a solution?

1 exception(s):

Exception # 0 (Magento Framework Config Dom ValidationException): Element & # 39; argument & # 39 ;: Duplicate key sequence (& # 39; title & # 39;) in the key identity restriction & # 39; blockArgumentName & # 39 ;.
Line: 1388

Exception # 0 (Magento Framework Config Dom ValidationException): Element & # 39; argument & # 39 ;: Duplicate key sequence (& # 39; title & # 39;) in the key identity restriction & # 39; blockArgumentName & # 39 ;.
Line: 1388

#1 MagentoFrameworkConfigDom->__construct() called at (vendor/magento/framework/ObjectManager/Factory/AbstractFactory.php:121)
#2 MagentoFrameworkObjectManagerFactoryAbstractFactory->createObject() called at (vendor/magento/framework/ObjectManager/Factory/Compiled.php:108)
#3 MagentoFrameworkObjectManagerFactoryCompiled->create() called at (vendor/magento/framework/ObjectManager/ObjectManager.php:56)
#4 MagentoFrameworkObjectManagerObjectManager->create() called at (vendor/magento/framework/Config/DomFactory.php:43)
#5 MagentoFrameworkConfigDomFactory->createDom() called at (vendor/magento/framework/View/Model/Layout/Update/Validator.php:141)
#6 MagentoFrameworkViewModelLayoutUpdateValidator->isValid() called at (vendor/magento/framework/View/Model/Layout/Merge.php:512)
#7 MagentoFrameworkViewModelLayoutMerge->_validateMergedLayout() called at (vendor/magento/framework/View/Model/Layout/Merge.php:488)
#8 MagentoFrameworkViewModelLayoutMerge->load() called at (generated/code/Magento/Framework/View/Model/Layout/Merge/Interceptor.php:206)
#9 MagentoFrameworkViewModelLayoutMergeInterceptor->load() called at (vendor/magento/framework/View/Layout/Builder.php:86)
#10 MagentoFrameworkViewLayoutBuilder->loadLayoutUpdates() called at (vendor/magento/framework/View/Layout/Builder.php:63)
#11 MagentoFrameworkViewLayoutBuilder->build() called at (vendor/magento/framework/View/Layout.php:257)
#12 MagentoFrameworkViewLayout->build() called at (vendor/magento/framework/View/Layout.php:882)
#13 MagentoFrameworkViewLayout->getBlock() called at (generated/code/Magento/Framework/View/Layout/Interceptor.php:414)
#14 MagentoFrameworkViewLayoutInterceptor->getBlock() called at (vendor/magento/module-cms/Helper/Page.php:215)
#15 MagentoCmsHelperPage->prepareResultPage() called at (vendor/magento/module-cms/Controller/Noroute/Index.php:47)
#16 MagentoCmsControllerNorouteIndex->execute() called at (generated/code/Magento/Cms/Controller/Noroute/Index/Interceptor.php:24)
#17 MagentoCmsControllerNorouteIndexInterceptor->execute() called at (vendor/magento/framework/App/Action/Action.php:108)
#18 MagentoFrameworkAppActionAction->dispatch() called at (vendor/magento/framework/Interception/Interceptor.php:58)
#19 MagentoCmsControllerNorouteIndexInterceptor->___callParent() called at (vendor/magento/framework/Interception/Interceptor.php:138)
#20 MagentoCmsControllerNorouteIndexInterceptor->MagentoFrameworkInterception{closure}() called at (vendor/magento/framework/Interception/Interceptor.php:153)
#21 MagentoCmsControllerNorouteIndexInterceptor->___callPlugins() called at (generated/code/Magento/Cms/Controller/Noroute/Index/Interceptor.php:39)
#22 MagentoCmsControllerNorouteIndexInterceptor->dispatch() called at (vendor/magento/framework/App/FrontController.php:159)
#23 MagentoFrameworkAppFrontController->processRequest() called at (vendor/magento/framework/App/FrontController.php:98)
#24 MagentoFrameworkAppFrontController->dispatch() called at (vendor/magento/framework/Interception/Interceptor.php:58)
#25 MagentoFrameworkAppFrontControllerInterceptor->___callParent() called at (vendor/magento/framework/Interception/Interceptor.php:138)
#26 MagentoFrameworkAppFrontControllerInterceptor->MagentoFrameworkInterception{closure}() called at (vendor/magento/module-store/App/FrontController/Plugin/RequestPreprocessor.php:99)
#27 MagentoStoreAppFrontControllerPluginRequestPreprocessor->aroundDispatch() called at (vendor/magento/framework/Interception/Interceptor.php:135)
#28 MagentoFrameworkAppFrontControllerInterceptor->MagentoFrameworkInterception{closure}() called at (vendor/magento/module-page-cache/Model/App/FrontController/BuiltinPlugin.php:73)
#29 MagentoPageCacheModelAppFrontControllerBuiltinPlugin->aroundDispatch() called at (vendor/magento/framework/Interception/Interceptor.php:135)
#30 MagentoFrameworkAppFrontControllerInterceptor->MagentoFrameworkInterception{closure}() called at (vendor/magento/framework/Interception/Interceptor.php:153)
#31 MagentoFrameworkAppFrontControllerInterceptor->___callPlugins() called at (generated/code/Magento/Framework/App/FrontController/Interceptor.php:26)
#32 MagentoFrameworkAppFrontControllerInterceptor->dispatch() called at (vendor/magento/framework/App/Http.php:116)
#33 MagentoFrameworkAppHttp->launch() called at (vendor/magento/framework/App/Bootstrap.php:261)
#34 MagentoFrameworkAppBootstrap->run() called at (pub/index.php:40)

Thanks in advance!

javascript: js node variable injection in single response directly to client DOM

this is what i did
sending the JSX backward syntax directly to the client through express to inject the variable & # 39; foo & # 39; directly in the client's DOM (which you can see in the image below)

enter the description of the image here

Now what I want to achieve is,
to send the index.html file together with the injected variable that comes from the file where the server is written (node ​​/ express).
NOTE! Display engines are not allowed, it should be as simple as possible.

javascript: refactor two functions with the createElement and DOM operations

I am trying to refactor these two functions, I am also thinking of creating functional tests, but my approaches have not worked.
I would really appreciate new ways to reuse my code.
Thank you

createMenuItems(providers, selected) {
  for (let i = 0; i < providers.length; i++) {
    const item = document.createElement('li');
    item.className = 'provider-item';
    const imageDiv = document.createElement('div');
    const provider = providers(i);
    const name =;
    imageDiv.className = `${'provider-item-view-mobile item-view-mobile '}${name.toLowerCase()}`;
    item.addEventListener('click', () => {
      this.changeProvider(provider, name, this.options.isL);
    const title = document.createElement('div');
    title.className = 'title-item-view-mobile';
    title.innerHTML = name.toUpperCase();
  const providersName = providers(selected).name;

  return this.holder;

createMenuItems(list, selected) {
  for (let i = 0; i < list.length; i++) {
    const item = document.createElement('li');
    item.className = 'carousel-item list-item';
    const content = document.createElement('div'); = list(i).id;
    content.className = 'list-item-holder';
    content.addEventListener('click', evt => {

    const container = document.createElement('div');
    container.className = 'list-item-container';

    const background = document.createElement('div');
    background.className = 'list-thumb'; = `url(${  list(i).imagSrc  })`;


    const text = document.createElement('div');
    text.className = 'list-item-text';
    text.innerHTML = list(i).title;

xss: DOM access between tabs of the same origin

Consider the following website. Page A ( contains a login form and your password field has the attributes name Y id adjusted to "password". Page B ( has an XSS vulnerability that allows an attacker to inject JavaScript code. One opens page A in a browser tab and enters a password, but does not send it. Then, one opens another tab and visits page B there.

Since the pages have the same web origin, the Policy of the same origin does not restrict access between them and, from the browser view, the attacker's code is loaded from the source But the DOMs of the pages are not connected by any route that allows access to each other.

Can the injected JavaScript code of the attacker access the password field and the password entered? If so, could someone give a small example?

javascript – How to make search engines index dynamically created DOM page

Note: this answer is only about Google, I am not aware of how others handle this.

Google bot can now run JS on crawled pages, by using a headless browser (fully automated browser instance). But as it requires more resources (therefore, money) To run that browser, you will visit your pages less frequently than the normal crawler, which only analyzes the initial HTML.

In any case, if you want to have a better SEO, there are several options available, and it is up to you to decide which ones you are willing to take. Here are some:

Make your website work without JS

In plus cases (and your website definitely falls into that category as far as I can see), JS is not really necessary to fill your HTML with data. It is to add interactivity or to obtain data from an API, which could be done on the server side. In this situation, it is always good to turn off JS in your browser and see if everything is still working. The content should already be on your page, even if it's not pretty, and it should work. JS should only be there to improve everything for the user. The links should work, the forms should work. If you have buttons that lead to other pages, they should be links, with a real URL, even if your application is a SPA.

This will help bots understand your page and the architecture of your site (i.e. the site map). Not only will it help people with disabilities (blind, for example) who use a screen reader. And Google takes that into account, which is good.

Serving dynamic content

The first obvious option that comes to mind is to process the data server side and render HTML pages on the fly. If you are only comfortable with JS, you can search NodeJS and create a server using a module such as ExpressJS or HapiJS, for example. There are tons of tutorials that you can find. Or, if you know other languages, you can do it in Python, PHP, Java …

Second option, if you really don't know how, or you don't want to work on the server side, you could look for static website generators, like Hugo. Write templates, define some data and, once finished, generate HTML pages and host them on a static server. That does not prevent you from having Javascript in the front-end to improve the page, by the way. But the content is already there.

Another solution, usually for more complex applications, is the representation of the server side. You run the page on your server in a browser-like context (It's not really a browser, but JS runs in the context of your page), JS fills the DOM and the updated HTML is what is sent to the client. JS can be used on the client side to do more work. It is becoming quite popular with existing frames. For example, if you write an application using VueJS, you can use NuxtJS or Vue-server-render to pre-render the HTML in a state that is only obtained after running JS. If that is not something you want to analyze, you can also use a paid service like SEO4Ajax, which will run your pages in a browser and maintain a cached version of the final HTML, so that it can serve bots such as the Google bot. We used that in our company for a while, it worked very well.

Leaving a good impression

Finally, if you want to have a higher ranking, your site must be of high quality. For example, at this time, it is not compatible with https. You are losing points here.

It doesn't have much text, which makes it less valuable.

Doesn't have a

, or really any page structure apart from divs.

It does not have Open Graph labels, which will help to display beautiful thumbnails on Twitter, Facebook or other services to share:
enter the description of the image here

It has no structured data to help trackers understand what your page is about, and which ones could be used to display your website in a pleasant way in search results:

enter the description of the image here

There are tons of other things to take care of, but the most important thing is to know that trackers become more and more intelligent. Therefore, no matter what you do, if your website is of poor quality and does not have great content, people will not like it. And if they don't like it, there's a good chance that Google won't do it either. Create your site with passion, see what crawlers suggest you do to improve it (for example, PageSpeedIndex, Google guidelines) and your website will eventually grow. It must be fast, it must be light. It should work fine on mobile devices.

magento2 – Exception # 0 (Magento Framework Config Dom ValidationException): Element & # 39; reference & # 39 ;: This element is not expected

I receive the following error when I go to the custom simple product details page.
It is working when you go to the simple product details page. I am using the theme magento porto and recently migrated from magento 1.9 to magento 2.3.3

main.INFO: cache file with combined design: LAYOUT_frontend_STORE1_40b0d6346f25da66374a88a3ad4a3a7b9_page_layout_merged and takes care of the default values, catalog_product_view, catalog_product_view_id_1053, catalog_product_viewMsku_JM_CK. Element & # 39; reference & # 39 ;: this element is not expected.
Line 1
[] []
[2020-01-28 13:15:42] main.CRITICAL: Element & # 39; reference & # 39 ;: This element is not expected.
Line 1

wordpress: will redesigning my site affect my SEO if my URLs and content remain the same but the DOM structure of the pages changes radically?

I have a great WordPress site in operation with which I earn money because SEO has been perfect for years. I really want to redesign the site (the design is 12 years old now) and I want to use Elementor.

The URLs will remain exactly the same and the content will remain virtually the same, but the "DOM" structure will change a lot (mainly because Elementor adds tons of DOM elements.

So, will this affect my SEO?

Is this JavaScript vulnerable to XSS based on dom?

I was trying and I found a reflection point js. If I send the following request:"'-confirm(1)-'

I can see the following in the server response:

Is this code vulnerable to XSS based on Dom? If so, what burden could an alert box attempt to activate?

I already tried to close the tag but < and > are filtered