7 – Enabling field translation for content type causes node to not show value for that field

I am using Drupal version 7.80.
I have a content type called “Public Resource” that has a bunch of fields. The content type has “Enabled, with field translation” for the Multilingual support.
Up until now we had never tried to translate any of the nodes though.
This changed and I was tasked with making sure the nodes are translatable.

I tried to translate one of the nodes. One of the fields called “Countries and Regions” is a field that is generated from a taxonomy and when I go to translate it the label says:
Countries & Regions (all languages)
which I figured out means that I have to set this field to be translatable.
When I go to manage field “Countries & Regions” on the content type settings is the “field translation” section. There is a link that says “Enable translation”. This was why my field had “all languages” showing up by the label when I tried to translate a node.

I clicked the “Enable translation” button and it opened up this window:
enter image description here

and I clicked confirm. It took a while to complete but it did so without any errors showing.

I then go back to my node I want translated and the English version of the node doesn’t have any data showing for “Countries and Regions”.

Here is a picture of the node before enabling translation of that field:
enter image description here

and here is a picture of the node after enabling translation of that field:
enter image description here

and if I go to the edit page of the node it shows that there is a value set for Countries and Regions for the node but it is just not showing it on the view node page:

enter image description here

Does anyone know why my values for the field that was just recently enabled for field translation are not showing up???

Xhumanity Reaches To New Heights After Enabling Bsc Staking And Farming

With the fast adoption of social media platforms and blockchain technology to promote social products and services, opportunities abound in the crypto ecosystem are certainly unlimited.

In a bid to offer better opportunities to crypto enthusiasts, the team at xHumanity is pleased to announce that new staking and BSC farming are ready and further process can be followed at https://app.xhumanity.org/

Furthermore, BEP20 XDNA deposit is also enabled at BitMart. For BSC farming, you can stake XDNA for up to 266% APY. And for staking, you can stake XDNA up to 149% APY.

Reduced Size Image

BSC Airdrop

In order to celebrate the new additions, xHumanity is very happy to announce that we are going to do a Giveaway (Airdrop) Event starting from Monday, 3rd May, 2021 with a 5,000 USD reward pool.

xHumanity Vision

xHumanity is born with the hope for a better world. Based on blockchain technology, xHumanity is an application that supports community building and social cross-interaction in both online and offline environments and distribute equity rewards.

The mandate of xHumanity is to revolutionize the present-day social media landscape, by reinventing human values and algorithms to create a better and more transparent social community where each member would be able to vote in the direction of a project.

xHumanity looks to leverage the power of blockchain technology as it is a technology that looks set to have the potential of contributing to the evolution of the Next Generation Internet and a viable tool to achieving high levels of Distributed Trust seamlessly and unobtrusively.

About xHumanity

xHumanity is an innovative blockchain project and a social community where users are empowered to leverage on the gains of social media marketing. Whether you are a new user or you have been on the xHumanity protocol for some time now, the project helps to interact with like-minded individuals, freely air your views, and network with celebrities.

xHumanity directly connects to centralized social networking platforms like Twitter, YouTube, Instagram, Facebook, and LinkedIn. Investors looking for where to earn a decent ROI can farm, lend, and stake their capital to earn xDNA tokens.

More Information at:

Website: https://xhumanity.org/

ETH Explorer: https://etherscan.io/token/0x8e57c27761EBBd…b92CeB51a358AbB
BSC Explorer: https://bscscan.com/token/0x80dba9c32b7ab54…5522e24c0ba4c24

office 365 – Is Custom Script Enabling required for PNP PowerShell?

We are generating a PNP Powershell to copy any document library files to file share. The issue we are facing is with “Get-PnPListItem” command. When we try with a tenant that has custom script enabled in Admin tenant, we are getting all values. But if we try with any new trial tenant, which does not have these setting, we are not getting the Title values.

enter image description here

enter image description here

I am not able to find out any document where I can find the pre-requisite for PNP-Powershell. Can someone tell that is it required or we are missing something else?

Note – We have Provided permission by “https://microsoft.com/devicelogin” URL.

Enabling HTTPS on all Synology ports

I’m attempting to set up external access for a couple services on my Synology DiskStation. I have a cert created from LetEncrypt (using the DSM’s GUI to do so) and I can access https://mysynology.synology.me:5001 just fine but any of my other externally accessible ports are only accessible via HTTP. Otherwise they complain “This site can’t provide a secure connection”.

I’m guessing there’s a config error somewhere that I’m missing but I haven’t found any information in any guides.

postfix – Trouble enabling mail_crypt in dovecot / SASL authentication failed

Ok, I tried to enable mail-crypt but it’s being weird. I’m using https://doc.dovecot.org/configuration_manual/mail_crypt_plugin/#ec-key.

I ran:

cd $HOME
openssl ecparam -name prime256v1 -genkey | openssl pkey -out ecprivkey.pem
openssl pkey -in ecprivkey.pem -pubout -out ecpubkey.pem

I edited the dovecot config to:

. . .
mail_max_userip_connections = 120
. . .
mail_plugins = $mail_plugins mail_crypt
plugin {
  mail_crypt_global_private_key = </home/ec2-user/ecprivkey.pem
  mail_crypt_global_public_key = </home/ec2-user/ecpubkey.pem
  mail_crypt_save_version = 2
}
. . .

I see in the logs now:

deliver       | Apr 15 02:43:29 ip-172-31-0-35 postfix/submission/smtpd(19059): warning: inet-MY IP-1.bos.netblazr.com(MY IP): SASL PLAIN authentication failed: generic failure
deliver       | Apr 15 02:43:29 ip-172-31-0-35 postfix/submission/smtpd(19059): warning: SASL authentication failure: cannot connect to saslauthd server: No such file or directory
deliver       | Apr 15 02:43:29 ip-172-31-0-35 postfix/submission/smtpd(19059): warning: inet.MY IP.bos.netblazr.com(MY IP): SASL LOGIN authentication failed: generic failure
. . .
deliver       | Apr 15 02:44:08 ip-172-31-0-35 postfix/smtpd(22684): NOQUEUE: reject: RCPT from mail-qk1-f176.google.com(209.85.222.176): 451 4.3.5 <MY EEMAIL>: Recipient address rejected: Server configuration problem; from=<connarpierce@gmail.com> to=<MY EMAIL> proto=ESMTP helo=<mail-qk1-f176.google.com>
deliver       | Apr 15 02:44:08 ip-172-31-0-35 postfix/smtpd(22684): disconnect from mail-qk1-f176.google.com(209.85.222.176) ehlo=2 starttls=1 mail=1 rcpt=0/1 bdat=0/1 quit=1 commands=5/7

I wonder why SASL is now enabled for postfix to work/authenticate (when it’s not if I turn off mail_crypt).

I’m guessing Server configuration problem is the problem here…

Any suggestions where I should look?

Enabling debugging with broken screen and usb keyboard (Google assistant working)

Is there a way to enable USB debugging with broken display – black screen and touches are not registering.
Ultimately I want to control my phone (answer phone calls, see messages, restore images, access bank mobile 2fa) through https://github.com/Genymobile/scrcpy, but it requires USB debugging mode.

Most tutorials make use of USB keyboard/mouse but for some reason they are not functioning (Oneplus 5t), and I have tested adapter+keyboard on different phone and it works.
What I have at my disposal

  • Unlockable phone – fingerprint sensor
  • Google assistant – it responds to “hey google”
  • Phone is connected to Wi-Fi and I can install apps through google play store on my PC

configuration – Magento Redirects to Admin Dashboard after enabling Loadbalancer

My magnto site was working fine, recently i enabled load balancer, after enabling load balancer i was auto redirected to Admin Dashboard on any action.

I tried changing session from files to redis still i get same issue.

Below is my env file code : please help me with way to fix it

return [
    'backend' => [
        'frontName' => 'admin'
    ],
    'crypt' => [
        'key' => 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'
    ],
    'session' => [
        'save' => 'redis',
        'redis' => [
            'host' => 'xxxredis.cache.amazonaws.com',
            'port' => '6379',
            'password' => '',
            'timeout' => '302.5',
            'persistent_identifier' => '',
            'database' => '7',
            'compression_threshold' => '2048',
            'compression_library' => 'gzip',
            'log_level' => '4',
            'max_concurrency' => '6',
            'break_after_frontend' => '500',
            'break_after_adminhtml' => '30',
            'first_lifetime' => '600',
            'bot_first_lifetime' => '60',
            'bot_lifetime' => '7200',
            'disable_locking' => '0',
            'min_lifetime' => '600',
            'max_lifetime' => '2592000',
            'sentinel_master' => '',
            'sentinel_servers' => '',
            'sentinel_connect_retries' => '5',
            'sentinel_verify_master' => '0'
        ]
    ],
    'db' => [
        'table_prefix' => '',
        'connection' => [
            'default' => [
                'host' => 'xxxrds.amazonaws.com',
                'dbname' => 'xxx',
                'username' => 'xxx',
                'password' => 'yyy',
                'active' => '1',
                'model' => 'mysql4',
                'engine' => 'innodb',
                'initStatements' => 'SET NAMES utf8;',
                'driver_options' => [
                    1014 => false
                ]
            ]
        ]
    ],
    'resource' => [
        'default_setup' => [
            'connection' => 'default'
        ]
    ],
    'x-frame-options' => 'SAMEORIGIN',
    'MAGE_MODE' => 'default',
    'cache_types' => [
        'config' => 1,
        'layout' => 1,
        'block_html' => 1,
        'collections' => 1,
        'reflection' => 1,
        'db_ddl' => 1,
        'eav' => 1,
        'customer_notification' => 1,
        'full_page' => 1,
        'config_integration' => 1,
        'config_integration_api' => 1,
        'translate' => 1,
        'config_webservice' => 1,
        'amasty_shopby' => 1,
        'vertex' => 1,
        'compiled_config' => 1
    ],
    'install' => [
        'date' => 'Thu, 20 Apr 2017 09:50:19 +0000'
    ],
    'downloadable_domains' => [
        '13.233.26.73',
        'www.orientbell.com',
        'ostag.orientbell.com'
    ],
    'queue' => [
        'consumers_wait_for_messages' => 1
    ],
    'cache' => [
        'frontend' => [
            'default' => [
                'id_prefix' => '190_',
                'backend' => 'Magento\Framework\Cache\Backend\Redis',
                'backend_options' => [
                    'server' => 'redis.cache.amazonaws.com',
                    'database' => '10',
                    'port' => '6379',
                    'password' => '',
                    'compress_data' => '1',
                    'compression_lib' => ''
                ]
            ],
            'page_cache' => [
                'id_prefix' => '190_',
                'backend' => 'Magento\Framework\Cache\Backend\Redis',
                'backend_options' => [
                    'server' => 'redis.cache.amazonaws.com',
                    'database' => '11',
                    'port' => '6379',
                    'password' => '',
                    'compress_data' => '0',
                    'compression_lib' => ''
                ]
            ]
        ],
        'allow_parallel_generation' => false
    ],
    'lock' => [
        'provider' => 'db',
        'config' => [
            'prefix' => ''
        ]
    ],
    'directories' => [
        'document_root_is_pub' => false
    ]
];