How to transfer a site from DRUPAL to WORDPRESS?

Question

Drupal

and how to be with a database after all there users?

Answer 1

If by some regular means, then no way.
And if you do a sql-export from a drupal database to wordpress format?
Through phpmyadmin write sql query and export. And also, import into the wordpress database.
Or you can try to write a script that generates an unloading of users from Drupal in xml, and import it into wordpress.

Answer 2

A signal comes to the network card via TCP, it extracts a packet from it and redirects it to the OS kernel, the kernel is already looking at which application to give this packet to. It finds Apache and passes it to it, it parses the package, selects the request, parses the request and further through the program.

Answer 3

Koterov's book PHP in the original fully describes the work of a web server, it is a very useful book! I recommend to read!

Answer 4

All this can be implemented from system to system in different ways. But on a normal computer, in most cases, it works like this. The OS (more precisely, the network card driver) receives a hardware interrupt when data arrives on the card. By the way, there is a so-called mechanism of "covered interrupts". Without going into details, interrupts will not come on every piece of data received by the card, but only when the software allows itself to be interrupted. That is: received an interrupt, disabled interrupts, began to process everything that came and comes, finished, allowed interrupts. Depending on the system or its settings, the driver may already be doing something with the data. I deliberately do not use the word "package", because so far it is only data that is in the buffer. Then after all the checks, they can be passed to the OS networking stack. The network stack, like the driver itself, is usually a kernel module. In fact, the network stack is a highly configurable and multi-layered / multi-layered and complex subsystem of the kernel, and usually represents not one module, but many. At each level, depending on its setting and / or data type (it is now appropriate to call them frames / packets / datagrams), a decision can be made what to do with it next. For example: forward somewhere, or skip, or answer them directly in the kernel, without passing it up to the user-spice, or still pass. Now, if this is your package, that is, your / correct ip, if the port is open for listening, for example, by a WEB server (80 / tcp), using the socket mechanism described above, then it will be transferred to the user-space web server for processing. Servers can also process it differently. Apache, for example, at least its early versions, didn’t bother much, allocated something to each connection along the stream that would process this request, and left to listen further. But heavily loaded servers will not be able to work this way, because streams "weigh" a lot, so there are still a lot of more advanced ways of processing requests by the server. By the way, there are servers that live right in the core. The zoo of servers, just like the network stacks, is large and too complex for one post. There will be time to describe more fully and competently. But "in a nutshell" should be clear. But heavily loaded servers will not be able to work this way, because streams "weigh" a lot, so there are still a lot of more advanced ways of processing requests by the server. By the way, there are servers that live right in the core. The zoo of servers, just like the network stacks, is large and too complex for one post. There will be time to describe more fully and competently. But "in a nutshell" should be clear. But heavily loaded servers will not be able to work this way, because streams "weigh" a lot, so there are still a lot of more advanced ways of processing requests by the server. By the way, there are servers that live right in the core. The zoo of servers, just like the network stacks, is large and too complex for one post. There will be time to describe more fully and competently. But "in a nutshell" should be clear.

Answer 5

Apache hangs on port 80 and parses what comes to it from http. Then it passes what has already come to your code if the Apache settings mean it.