wp query: modifying raw data $ _POST at the beginning of the life cycle

Is there a specific way of plugin to modify superglobals directly before they are used? Assuming the following code was in a plugin called aaa, one could imagine that this would run fairly early in the request lifecycle. While the code is running, when other plugins use the data, it has not been modified.

// file location: wp-content / plugins / aaa / aaa.php

function interfere_with_things(){

    // skip anything not applicable
    if($_SERVER('REQUEST_METHOD') !== 'POST' || empty($_POST('something'))){return;}

    // change something in the $_POST
    $_POST('something') = str_replace('cats', 'dogs', $_POST('something'));


add_action('init', 'interfere_with_things', 1);

centos7 – How do I prevent users from modifying network proxy settings in gnome (CentOS 7)?

I have the host and port settings in / etc / environment to persist all users. My dconf lock file contains:


Users can still disable the network proxy through the settings menu at will. We are using Privoxy as a content filter and we must prevent users from skipping it. Thank you.

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 DOM.style.width 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.


Java, Jasper Reports – Reports that the user can change without modifying from the project source

The user wishes to be able to edit the report generated by jasper without the need to call a developer.

For example: letterheads, footers, location of fields to display, etc.

That is, a changing report over time.

Security: What prevents a knowledgeable person from modifying their bitcoin data?

Bitcoin is not stored on a machine, but it is kept in a distributed public book known as blockchain. The blockchain is a database that is replicated on the machines of all who participate by running the bitcoin software. This means that the database you have locally on your machine is only a copy of which the network as a whole agrees that it is the correct and indisputable accounting book.

The process by which all participants agree which chain is the true valid chain is called mining, which uses a Proof of Work mechanism to allow a participant to confirm a new block in the chain approximately every 10 minutes. The process by which a participant is selected is pseudorandom and probabilistic, depending on the amount of job they do, which generally corresponds to the amount of electricity that they irreversibly consume to perform the calculation at the current tip of the chain.

The cost of electricity to get the job done is one of the theoretical elements of the Bitcoin game that keeps it safe, because it means that any participant who tries to adjust the ledger to favor will have to spend money and consume electricity, but their chances of success It is extremely small, since they would need to perform more than 50% of the total global work done at the current end of the blockchain to stay ahead honest majority. Most participants are honest because it can be profitable to be honest, but being dishonest generates losses unless you are sure you have more than 50% of the global work done in Bitcoin.

The chain is secured by cryptographic hashes, so any attempt to change anywhere in the ledger produces different hashes. Each block in the chain explicitly refers to the hash of the header of the previous block, and this value is also included in the header of the current block. This means that each block is committed to all blockchain history, and any attempt to rewrite part of the ledger would require rewriting the entire ledger history from the point of modification. Therefore, rewriting the history would require a greater amount of work than the total amount of work that was done between the block that was attempted to modify and the current point of the chain.

The ledger is a linear sequence of blocks that contain a set of transactions, where one of the transactions in the set is a coin base, which charges the fees of other transactions in the block and releases some previously unused bitcoins as part of a default launch program. Currently about 35/40 of all bitcoins have been launched and the remaining 5/40 will be released gradually over the next 120 years.

The other transactions in a block are regular transactions that have inputs and outputs. The entries of a transaction refer to the output of a previous transaction. The outputs contain a lock script, which is a set of prerequisites that must be met for that exit to be spent. Once the exit of a transaction has been spent, it cannot be spent again. This means that there is at any time, a set of exits of transactions not spent (UTXO) in the ledger, which is where all existing bitcoins are stored.

The relationship with a wallet is where this lock script comes. For all regular transactions, one of the prerequisites for unlocking the output and spending it is to provide a digital signature that matches a public key that is stored in the exit lock script. Only the person who has the private key corresponding to the public key is capable of producing said signature, and the message they sign is a hash of the transaction they are trying to spend, which guarantees that no one else can manipulate this transaction because they would invalidate the signature.

Therefore, a wallet is essentially a set of private keys that are used to unlock some bitcoins stored in some UTXO in the distributed public book. A wallet will compare the corresponding public key set with the entire UTXO set of the public ledger to determine which bitcoins are essentially "property" of this wallet. The amount of bitcoin in the UTXO set that the user can unlock corresponds to his balance.

A normal bitcoin software will get a copy of the entire ledger and listen if other nodes add new blocks, which transmit them through a point-to-point network. Several different connections are used to ensure that peers do not present false or outdated information. Each time a new block is created, approximately one every 10 minutes, the wallet will download the block and look through its set of transactions in search of which the wallet has the relevant private keys to unlock. Everything you can unlock is added to the balance, and this becomes again received bitcoin

To spend bitcoins, a user must select one or more UTXO for which he has the private key to unlock. They create a new transaction that refers to these UTXOs as inputs, and create a set of outputs that contain new blocking scripts, usually by including the public key hash of the person they wish to pay, which comes from bitcoin speak to They use for that payment. The amounts of bitcoin at the outflows of a transaction must be less than or equal to the amounts of the incoming UTXOs referred to in the transaction, and any difference is paid as the fee for the transaction. Then, the user will sign this transaction and transmit it through the point-to-point network.

A transaction must be valid for any other node in the p2p network to accept it. This means that the participant who receives a transaction will compare the accuracy of the UTXO set with their own copy of the ledger. If you modify something in your local copy of the ledger, it will not produce changes in the copy that no one else has made. If you tried to spend an amount that other participants do not agree with your property, then your transaction will be invalid and rejected by the network. It will never be included in a block, and the recipient will not receive anything.

In other words, any attempt to modify the data locally can only attempt to deceive itself, but it cannot deceive others. No one accepts anything you say as true: they verify it for themselves by verifying the historical accuracy of the ledger.

navigation – drupal 8 modifying the route of the menu items

I work in a drupal 8 application that uses the group module with the restriction of only one group per user. I want to be able to modify the menu items so that the user group identification is always in the url. this way I can use views with a group ID in the url.

I search and always go to the same pages with the same example that does not work for me.

Android Studio – (Kotlin + XML) Button moves when modifying text

The problem is when changing the text of the play button, through this code:

private fun checkState() {
        if (mp.isPlaying) {
            val trackinfo = songList(0).name
            play.text = "PLAYING: $trackinfo" //ESTO DA EL PROBLEMA
        } else {
            play.text = "PLAY"

I pass the layout code





The problem is that when you press the button in question this executes a song in the player and at the same time also passes the text of the song to the attribute of the "text" button, (there is another way to do this that is more correct since Android Studio Let me know, if you also know how to achieve it in a "clean" way I'm interested to know) it moves down, and the Linearlayout that has just below partially covers it.

Why this behavior?

Normal button
Button with added text

8 – Modifying the link form does not work for the node editing form

I have a type of content called landing_page. If I edit an existing node in the administrator /node/31/edit and I inspect the form I see id="node-landing-page-edit-form".

I can't make it work hook_form_FORM_ID_alter()?

I tried:

function MYTHEME_form_node_landing_page_edit_form_alter(&$form, FormStateInterface &$form_state, $form_id) {
  $form('field_message') = array(
    '#type' => 'item',
    '#title' => t('New article'),
    '#markup' => t('Test message'),

I also tried:

function MYTHEME_form_node_form_alter(&$form, FormStateInterface $form_state) {
  $form('field_message') = array(
    '#type' => 'item',
    '#title' => t('New article'),
    '#markup' => t('Test message'),

And I tried:

function MYTHEME_form_alter(&$form, FormStateInterface $form_state, $form_id) {
if ($form_id == 'node_landing_page_edit_form') {
// My code here

block editor – Gutenberg Additional CSS class without modifying the theme?

The "Advanced" option to add Additional CSS Classes For a Gutenberg block it seems useful. But, is there any way to define a CSS class to use in that post option other than going and adding a class of the whole topic?

(I expected some way to modify the CSS in a specific block without having to convert it into an HTML block).

views – Modifying twig files to display the elements side by side

I am working on views with embedded filters and my resulting fields of view have the following twig settings:

    {%- if field.label -%}
        {%- if field.label_element -%}
          <{{ field.label_element }}{{ field.label_attributes }}>{{ field.label }}{{ field.label_suffix }} 
        {%- else -%}
          {{ field.label }}{{ field.label_suffix }} 
        {%- endif %}
      {%- endif %}

        {%- if field.element_type -%}
          <{{ field.element_type }}{{ field.element_attributes }}>{{ field.content }}
        {%- else -%}
          {{ field.content }} 
        {%- endif %}

In this configuration the lable is showing above and then the text below. Is there a way to make them appear next to each other:

Current output:


Desired output:


Some help?!!