9 – Disable database delete if accidental module uninstallation

We are designing critical Website Project, and some of the site strcture like content type, fields are defined through module

  • we want if “Accidental Module Uninstallation” occurs, the database created with the module does not get deleted.

To store the database created, we are taking backup regularly through Cron job. But, we want the tables remains even after module is uninstalled.

Is it possible to keep data after module uninstalled?

Can the blog be online(the content created with above module) even if accidental module uninstallation occurs?

If module is re-enabled again: can the module integrate with previous data, and write new data?

Data created, and blogging content written are critical and expensive, we can not keep any flaws, even if in worst case scenario – anything worse happens.

Can anyone give some insight into this?

Edit : Even in worse case scenario, if Module gets deleted(uninstalled), we can not let single bit of data removed.
Suppose field data, by anyone’s mistake – if module gets deleted, Data should be present.

If data gets deleted with module uninstallation, it’s website design/development flaw, and blame always goes to the developer

theming – Disable links to username and date

I am pretty new in drupal development. One of my tasks require me to disable links to username and date fields generated inside diff_diffs_show function of diff.pages.inc file under diff module ( https://www.drupal.org/project/diff )

  // Generate table header (date, username, log message).
  $old_header = t('!date by !username', array(
    '!date' => l(format_date($old_node->revision_timestamp), "node/$node->nid/revisions/$old_node->vid/view", array('absolute' => 1)),
    '!username' => theme('username', array('account' => $node_revisions($old_vid))),
  ));
  $new_header = t('!date by !username', array(
    '!date' => l(format_date($new_node->revision_timestamp), "node/$node->nid/revisions/$new_node->vid/view", array('absolute' => 1)),
    '!username' => theme('username', array('account' => $node_revisions($new_vid))),
  ));

Can someone help me how I can alter this function so that the links are disabled? Basically, I want the username and date fields in plain texts instead of links. I know it’s not right to modify module function code directly, so can someone guide me on how to create a custom module to alter this function and disable the links?

See this picture for reference – enter image description here

lg g2 – Disable popups on cancelled Sprint service on LG G2

You can root your device and then manually disable those popup settings by editing databases using SQLite editor app.

Some manufacturers put their custom apps as ordered by service providers. Theses apps do not have their own UI, but used by other service provider specific apps to get updated values from service provider as per customer-plan.

These apps change default values of certain actions, responses, service access in SQLite databases that are present in Android devices or build their databases which are accessed by Android system.

By using SQLite editor app, user can browse these databases manually and change values that seems to be connected with this pop-up issue. To browse these databases, device needs root access.

How can I disable mysql_native_password and mysql_old_password on MariaDB / MySQL?

I only want to use unix_socket as the sole authentication method.
Both mysql_native_password and mysql_old_password are installed and enabled by default, but I’d like to disable them.

I’m unable to uninstall them:

MariaDB ((none))> uninstall plugin mysql_native_password;
ERROR 1619 (HY000): Built-in plugins cannot be deleted            

I’ve followed the instructions here:
https://mariadb.com/kb/en/mysql_plugin/

I’ve created disabled_plugins.ini in /etc/mysql with contents:

disabled_plugins
mysql_old_password

Then:

MariaDB ((none))> mysql_plugin disabled_plugins DISABLE;
ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'mysql_plugin disabled_plugins DISABLE' at line 1

This is on WSL1 and 10.3.27-MariaDB-0+deb10u1-log Debian 10

Can someone help?

Thanks

system installation – When installing Ubuntu 18.04.5 Desktop from a USB flash drive, how do I disable `iio-sensor-proxy`?

I’m trying to install Ubuntu 18.04.5 Desktop on a computer using a USB flash drive (which I made with the official ISO file). However, for some reason, the screen orientation is always wrong after the installer is loaded.

My colleague has told me it’s caused by iio-sensor-proxy so, after the OS is installed, we just run apt remove iio-sensor-proxy to remove it and the removal doesn’t cause any problem.

But it’s very painful during the OS installation because of the wrong screen orientation as well as the weirdly mapped mouse movement. But for testing purpose, we want to wipe out the machine and re-install the OS often, so I want to see if I could fix or work around this issue.

Because the wrong orientation is caused by iio-sensor-proxy, I’m thinking about whether there is a way to tell the installer not to load it at all. So I’m wondering if there is something (maybe a file) I can add/edit on the flash drive installer to do this.

Alternatively, if there is no such a method as said in the previous paragraph, I’m wondering if there is something I may do at the beginning of the installation when the wrong orientation already happens. This is not ideal, but if I only need to suffer from the pain at the beginning of the installation and could have a normal user-experience in the following steps, it’s still acceptable.

factory reset – How can I disable recovery mode?

Is there a way to disable recovery mode so it won’t be possible to factory reset your phone?

Basically what I am trying to do, is that it should be impossible to factory reset the phone as there is no recovery partition.

(Example format the recovery partition, or hide the option of factory reset on the recovery menu, build a custom recovery etc.)

P.S.. I was thinking of maybe removing a system app (example package installer) and making it a user app, and therefore when you factory reset the phone it won’t start cause the system app is missing, but when I tried that, the phone wouldn’t start even without resetting it, as the system needs the system app to start, ( I thought that maybe even though I removed the app from being a system app, the phone would still start as it’s still there as a user app, and only after resetting the phone – that the user apps get deleted, the phone won’t start as it’s missing the app).

Thanks in advance

Woocommerce categories disable

I want to disable the ability for someone to pick a category when he uploads a product .
Hint : I want only to disable the option to pick a… | Read the rest of https://www.webhostingtalk.com/showthread.php?t=1839253&goto=newpost

repair – How do I disassemble FujiFilm X-T1 camera to disable the ISO dial lock button protection?

How to disassemble / take apart Fujifilm X-T1 and how to disable ISO Dial lock switch.

It is relatively easy to take apart FujiFilm X-T1. You only need one type of screwdriver, although the screws themselves are different. So as usual, make sure to have several small containers and a piece of paper to write down/draw where a particular screw came from. It took me less than half an hour. And I had no idea what I was doing. Took longer to document the process 🙂

The way the camera opens is, the top part comes loose and the back slides out, separating from the front. WARNING: DO NOT remove the top first. Just unscrew it and notice that it is loose and leave it be. The reason is that it has several short ribbon (film) cables, and if you lift it up first, you’re likely to disconnect or mis-align them, or worse!

So first remove all the screws that I will mention below in diagrams, then slide the back side out, and the then the top will easily lean back. The back side is preventing it from leaning back. Here in this photo you can see that I tried it at first without removing the backside:
enter image description here

As you’re removing the back side make sure to support the top so that it doesn’t fall, pulling on the cables. Back side also has ribbon cables but it’s much more easy to handle, they’re only attached towards the bottom (see image below).

So if you do everything right, no need to unplug any of the cables. If you’ve ever dealt with ribbon cables you know why I’m stressing this part so much. They and the ports they go into are very fragile and difficult to handle. Tweezers can scratch them and even cut the connection. (Here they’re not that big of a deal as in Fuji lenses I opened previously, but still why bother if you don’t have to right?)

So, lets do it step by step. 

1) Bottom: there are 8 screws – unscrew all

2) Front: only 1 (small) screw on the right side, peal off the rubber covering.enter image description here

Left/Right is when facing the camera.

3) Left: 2 above, 2 below (all behind the rubber)

4) Right: 2 above (behind the rubber) and one behind the USB door

5) Back side: Lift up the viewfinder rubber guard to reveal 2 screws, and flip up the LCD to reveal two screws there: enter image description here

The lower part behind the LCD has 4 more screws. Those ones only hold the LCD in place. Don’t remove them.

6) Once these screws are removed the camera can come apart. Again, don’t pull on the top part. Slide the back side out as in this diagram:enter image description here

enter image description here

It comes apart this way, so the middle sides belong to the front part. That’s why in the previous pic I’m pushing the top edge out with my index fingers and bottom with my thumbs.enter image description here

7) And it opens up like thisenter image description here

8) Now with the back cover down, the top part can be leaned backwards easily:enter image description here

9) And you have access to the ISO dial mechanism. Just unscrew that middle screw and follow the diagram to remove the evil silver ring. It actually snaps on/out. So if you ever wanted to put it back, it’s a possibility.enter image description here

10) And here’s how it looks like inside. enter image description here

Before doing this, I was wondering if there’s a spring inside etc, and that afterwards there would be a hole I would need to seal… but none of that!
Once you take out the ring and close up the camera, the button is still in place and presses down like before, except it has ZERO effect now! The ISO dial still clicks as you rotate it, same as before. It’s like the magic fairy came and took only this silly ISO dial lock “feature” away without any side effects, with an exception of course, that you actually have to do it all yourself 😉

How do I disable mouse history scrolling?

How Do you disable the ability to scroll through history using the mouse scroll button. The reason that I need to do it that I am programming and I find my scroll history pasted randomly through my code. I hate it and it need to be fixed.

Disable title block on edit screen for a custom post type

I have a custom post type with a custom block to collect required data and store it in post meta data or standard fields like title or slug, so I don’t want to display the Title block. I can’t disable title support in the CPT, because too much else depends on it.

The only successful attempt so far has been using CSS to target the id “post-title-0” of the for the title and can clearly enqueue a small CSS file depending on the post type, but I don’t want to depend on something set by WordPress that I can’t control; it feels that something in Javascript would be a better way to go if possible. I was wondering if WP provde any hooks for this but haven’t found any.

I’m a javascript novice, having started learning it in the last few weeks in order to write some custom blocks, so am not clear on the extent of what can be acheived with it. (I have 50 years experience of programming, just not in JS).

It would be OK to only hide the title until the post has been saved.

I did see one relevant post on here but it was for the Gutenberg plug-in and I didn’t know if I could adapt it for current versions.

Has anyone any ideas?