Free software

Window.event does not exist in Firefox. Different browsers have different event models. Firefox handles the events slightly different IE and Chrome and for that reason it has not worked. A work-around is to pass the event as an argument to the function:
<a onclick="testfunction(event);">
 //...
</a>

testfunction(e){
 evt = e || window.event;
 //...
}

or use a library like jQuery to avoid dealing with all the differences between the browsers.

First the excel file was converted to a CSV file using LibreOffice Calc.

Then using the web generator https://codebeautify.org/csv-to-sql-converter and entering some database specific details (tablename, columnname identifier, columnname targetvalue) and choosing "CSV to SQL(INSERT)" an SQL script was generated that inserts into each row with the identifier the corresponding value from the CSV file.

The output was saved as an .sql file.
A a database backup created.
Afterwards the sql-file was uploaded into phpMyAdmin as an import script and executed perfectly.

ProgrammingLanguage:

For local development it is usually a practise to spawn test containers on a local machine and run them all the time during development.
Also embedded broker/server is also an option, but RabbitMQ and Postgres don’t offer embedded solutions out of the box and setting a custom one would take too much time.
So what you can easily do is spawn local short lived docker containers with these technologies. 
A good and tested solution to this problem is using the Testcontainers test dependency. Test containers
So, with provided RabbitMQ and Postgres images, you just launch containers on Test Suite start and they get automatically destroyed on shutdown.

First of all check for a corrupt .htaccess file on your FTP server. Rename the existing one and try to visit your site. If nothing changed the .htaccess is not the reason for the error. In my case the solution was to rename the folder "plugins" in the folder wp-content. Then try to access the website again if you see the text of your website of course without any graphical elements the reason for the error is a corrupted plugin. Now create a new folder "plugins" in the folder wp-content and move one plugin from the old plugins folder to the new created folder. After every movement try to reload the website if it is possible to see the content it wasn't the corrupted plugin. In my case an internal plugin of wordpress "wp_smtp_mail" was the reason for the error. Hope my solution helps! Good luck!

The mainly difference, which help to decide the selecting decision for the software design is the embedded mode. H2 supports this kind of the mode while PostgreSQL doesn't support it. Further H2 is platform independent and mostly used for the small application and PostgreSQL only supports some kind of the OS.

The easiest way to get to the desktop version of a website is by selecting the desktop view link on the page itself - if it is provieded! Not every website has this option, so of course your described methods are usefull in this cases as a quick workaround.

Taggings:

It should be stated, that when Adblocker is installed, it will block also the content of some websites. But it is still possible to prevent sites from detecting the usage of an Adblocker.

Taggings:

On Mozilla Firefox, you can also do this by opening the menu to the right(three dots on top of each other) and checking "request desktop site". Requesting desktop is particularly useful for youtube videos of songs, because this way, you can lock your mobile device and still listen to the song, which is not possible through the youtube app.

Technology:

The problem can be solved by using a Nginx reverse proxy. Each application will be exposed through a corresponding sub-domain.

Dockerfile:

FROM nginx:alpine
COPY nginx.conf /etc/nginx/conf.d/default.conf
COPY proxy.conf /etc/nginx/includes/proxy.conf

proxy.conf:

proxy_redirect off;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_buffering off;
proxy_request_buffering off;
proxy_http_version 1.1;
proxy_intercept_errors off;

nginx.conf:

# pm config.
server {
listen 80;
server_name site1.myproject.com;
location / {
include /etc/nginx/includes/proxy.conf;
proxy_pass http://site1_webserver_1;
}
access_log off;
error_log /var/log/nginx/error.log error;
}
# api config.
server {
listen 80;
server_name site1.myproject.com;
location / {
include /etc/nginx/includes/proxy.conf;
proxy_pass http://site2_webserver_1;
}
access_log off;
error_log /var/log/nginx/error.log error;
}
# Default
server {
listen 80 default_server;
server_name _;
root /var/www/html;
charset UTF-8;
access_log off;
log_not_found off;
error_log /var/log/nginx/error.log error;
}

The proxy_pass is the name of the application's docker container.

Technology:

I will explain a solution for the popular Open-Source tool Filezilla. Other FTP tools might handle charset encoding differently.

FileZilla offers three different charset settings:

  1. Autodetect
  2. Force UTF-8
  3. Use custom charset

Per default, FileZilla tries to detect the correct charset on its own. If this doesn’t work and your server uses some custom charset encoding, you need to set it via the Site Manager. In the tab “Charset”, a custom charset encoding can be specified for each individual server. Once it’s set, the specified charset encoding will be used for all future connections to this server and the filenames will be correct.

Pages

Subscribe to Free software