[Version 2 Release] RaspberryPints - Digital Taplist Solution

[RandR+]

Changing the default date/time format in MySQL is beyond my abilities

apparently you cant just change the default date format. with the way that I do the SQL select I would have to add in logic to look for a date format field when doing the select but that would take a bit of bandwidth I don't have right now

 

[ba-brewer]

I see them too, I Think it is a problem with the forum program and not the browser.

 

[RandR+]

Anyone else seeing smiley faces in those code

Im seeing them too... Time to get a beer and figure out how to get : D (without spaces) to not be a smiley face

 

[day_trippr]

Thanks for the replies.
fwiw, I usually wrap fragments in code tags just to eliminate browser interpretation...

Cheers!

 

[esdill]

Anyone else seeing smiley faces in those code fragments or did my browser blow a fuse? Weird...

I see them too.

 

[DirtyRed07]

Hey everyone. I’ll start by saying I know next to nothing about coding. I tried to install Rpints to no avail, until someone on a fb group gave me a command to let it set up automatically. Did that, working great, except I need to change font color (I saw a post about that, but don’t know what to do to get to the right place to edit the text). Also, I’ve changed it to only display my 3 taps, but my background picture is nowhere near fitting the screen. Can someone please tell me how to fix these things like they’re talking to a kindergartener?? Much appreciated!

 

[RandR+]

I need to change font color

Most font color is in the style.css in the main directory you installed in (i.e. /var/www/html/style.css) you may need to give yourself permission to edit the file
from the terminal

type (change /var/www/html to your installation path if different)
sudo chmod +777 /var/www/html -R

Then you can open up style.css with the test editor, search for color
There will be background-color and color you will want to change the color entry to the color you want. Colors unusually are in hexadecimal. you can figure out the hex value of a color by searching the internet for a color picker. Save the file and refresh the webpage
There are multiple colors entry in the style.css you will need to change, the text above it will indicate what it is for.

my background picture is nowhere near fitting the screen

It looks it is either the monitor limiting the size or the internet browser. Does it fill the screen outside of kiosk mode?

 

[DirtyRed07]

Before installation of Rpints, the normal pi Home Screen fit just fine. Now it has a margin all the way around. I’d like to have an image as the background for my tap list, but when I upload the image it makes it huge on tap list.

 

[RandR+]

Now it has a margin all the way around.

Sounds like you changed the monitor resolution during install
look in /boot/config.txt
there should be hdmi_group and hdmi_mode if any lines start with # then they may have been replaced during install with your selection.

best to post what you see in that file here

 

[DirtyRed07]

Pro

Sounds like you changed the monitor resolution during install
look in /boot/config.txt
there should be hdmi_group and hdmi_mode if any lines start with # then they may have been replaced during install with your selection.

best to post what you see in that file here
[/QUOTE

 

[RandR+]

Pro

Linux doesn't like the . in ./boot/config.txt
the second time it found it
the third time you spelled config congig

Run
tail /boot/config.txt

 

[DirtyRed07]

Linux doesn't like the . in ./boot/config.txt
the second time it found it
the third time you spelled config congig

Run
tail /boot/config.txt

That found it, ps the max resolution on my monitor is 1600x900, thanks.

 

[RandR+]

max resolution on my monitor is 1600x900, thanks.

From that config it looks like you setup 1920 x 1080 as your monitor during installation.

I think just removing the hdmi_group and hdmi_mode from /boot/config.txt should fix your issue since it was working fine before the install.
In the terminal run:
sudo vim /boot/config.txt
hit i
use the down arrow to go through the lines, if you see lines that starts with #hdmi_group or #hdmi_mode, remove the starting #
when you get to the end of the file type # infront of the hdmi_grup=1 and hdmi_mode=16 lines (right above the display_rotate line)
hit Escape button on the keyboard
type :w
type :q

reboot the pi

 

[DirtyRed07]

Linux doesn't like the . in ./boot/config.txt
the second time it found it
the third time you spelled config congig

Run
tail /boot/config.txt

That found it,

From that config it looks like you setup 1920 x 1080 as your monitor during installation.

I think just removing the hdmi_group and hdmi_mode from /boot/config.txt should fix your issue since it was working fine before the install.
In the terminal run:
sudo vim /boot/config.txt
hit i
use the down arrow to go through the lines, if you see lines that starts with #hdmi_group or #hdmi_mode, remove the starting #
when you get to the end of the file type # infront of the hdmi_grup=1 and hdmi_mode=16 lines (right above the display_rotate line)
hit Escape button on the keyboard
type :w
type :q

reboot the pi

nothing happened when I hit escape, I hit w and q anyway then closed the terminal opened a new one and rebooted. Still have borders and that box that says the input isn’t supported.

 

[RandR+]

nothing happened when I hit escape, I hit w and q anyway

It will look like nothing happened when you hit Escape, but you wont be able to type in the file any more.
You need to type : then w then hit enter
it will appear in the lower left corner

and type : then q then hit enter

the :w indicates write the file
:q indicates quit and will return you to the terminal

 

[DirtyRed07]

Linux doesn't like the . in ./boot/config.txt
the second time it found it
the third time you spelled config congig

Run
tail /boot/config.txt

That found it,

From that config it looks like you setup 1920 x 1080 as your monitor during installation.

I think just removing the hdmi_group and hdmi_mode from /boot/config.txt should fix your issue since it was working fine before the install.
In the terminal run:
sudo vim /boot/config.txt
hit i
use the down arrow to go through the lines, if you see lines that starts with #hdmi_group or #hdmi_mode, remove the starting #
when you get to the end of the file type # infront of the hdmi_grup=1 and hdmi_mode=16 lines (right above the display_rotate line)
hit Escape button on the keyboard
type :w
type :q

reboot the pi

nothing happened when I hit escape, I hit w and q anyway then closed the terminal opened a new one and rebooted.

It will look like nothing happened when you hit Escape, but you wont be able to type in the file any more.
You need to type : then w then hit enter
it will appear in the lower left cornerView attachment 718054
and type : then q then hit enter
View attachment 718056

the :w indicates write the file
:q indicates quit and will return you to the terminal

Still have borders and the input not supported box scrolling around

 

[RandR+]

Still have borders and the input not supported box scrolling around

can you post
tail -f /boot/config.txt
again?

 

[DirtyRed07]

Linux doesn't like the . in ./boot/config.txt
the second time it found it
the third time you spelled config congig

Run
tail /boot/config.txt

That found it,

From that config it looks like you setup 1920 x 1080 as your monitor during installation.

I think just removing the hdmi_group and hdmi_mode from /boot/config.txt should fix your issue since it was working fine before the install.
In the terminal run:
sudo vim /boot/config.txt
hit i
use the down arrow to go through the lines, if you see lines that starts with #hdmi_group or #hdmi_mode, remove the starting #
when you get to the end of the file type # infront of the hdmi_grup=1 and hdmi_mode=16 lines (right above the display_rotate line)
hit Escape button on the keyboard
type :w
type :q

reboot the pi

nothing happened when I hit escape, I hit w and q anyway then closed the terminal opened a new one and rebooted.

can you post
tail -f /boot/config.txt
again?

 

[RandR+]

nothing happened when I hit escape, I hit w and q anyway then closed the terminal opened a new one and rebooted.

Are you doing anything else after the reboot? its odd to see the lines commented out so many times then added back in at the end.

It may be Pi OS doing it automatically if nothing is in the config file. So if you aren't doing anything else try changing
hdmi_group to 2 and hdmi_mode to 82
as in do the same steps to edit the file as before but instead of putting # infront of the last lines change 1 to 2 and 16 to 82
then hit escape
type :
type w
type :
type q

and reboot then post
tail /boot/config.txt
again

 

[DirtyRed07]

Linux doesn't like the . in ./boot/config.txt
the second time it found it
the third time you spelled config congig

Run
tail /boot/config.txt

That found it,

From that config it looks like you setup 1920 x 1080 as your monitor during installation.

I think just removing the hdmi_group and hdmi_mode from /boot/config.txt should fix your issue since it was working fine before the install.
In the terminal run:
sudo vim /boot/config.txt
hit i
use the down arrow to go through the lines, if you see lines that starts with #hdmi_group or #hdmi_mode, remove the starting #
when you get to the end of the file type # infront of the hdmi_grup=1 and hdmi_mode=16 lines (right above the display_rotate line)
hit Escape button on the keyboard
type :w
type :q

reboot the pi

nothing happened when I hit escape, I hit w and q anyway then closed the terminal opened a new one and rebooted.

can you post
tail -f /boot/config.txt
again?

Are you doing anything else after the reboot? its odd to see the lines commented out so many times then added back in at the end.

It may be Pi OS doing it automatically if nothing is in the config file. So if you aren't doing anything else try changing
hdmi_group to 2 and hdmi_mode to 82
as in do the same steps to edit the file as before but instead of putting # infront of the last lines change 1 to 2 and 16 to 82
then hit escape
type :
type w
type :
type q

and reboot then post
tail /boot/config.txt
again

This fixed the border issue, but I still have the opaque box scrolling around saying input not support

 

[RandR+]

I still have the opaque box scrolling around saying input not support

its progress. Usually Input Not Supported is from the monitor itself not the Pi. How are you connected to the Pi?

 

[DirtyRed07]

Linux doesn't like the . in ./boot/config.txt
the second time it found it
the third time you spelled config congig

Run
tail /boot/config.txt

That found it,

From that config it looks like you setup 1920 x 1080 as your monitor during installation.

I think just removing the hdmi_group and hdmi_mode from /boot/config.txt should fix your issue since it was working fine before the install.
In the terminal run:
sudo vim /boot/config.txt
hit i
use the down arrow to go through the lines, if you see lines that starts with #hdmi_group or #hdmi_mode, remove the starting #
when you get to the end of the file type # infront of the hdmi_grup=1 and hdmi_mode=16 lines (right above the display_rotate line)
hit Escape button on the keyboard
type :w
type :q

reboot the pi

nothing happened when I hit escape, I hit w and q anyway then closed the terminal opened a new one and rebooted.

can you post
tail -f /boot/config.txt
again?

Are you doing anything else after the reboot? its odd to see the lines commented out so many times then added back in at the end.

It may be Pi OS doing it automatically if nothing is in the config file. So if you aren't doing anything else try changing
hdmi_group to 2 and hdmi_mode to 82
as in do the same steps to edit the file as before but instead of putting # infront of the last lines change 1 to 2 and 16 to 82
then hit escape
type :
type w
type :
type q

and reboot then post
tail /boot/config.txt
again

This fixed the border issue, but I still have the opaque box scrolling around saying input not support

its progress. Usually Input Not Supported is from the monitor itself not the Pi. How are you connected to the Pi?

Progress for sure! HDMI

 

[RandR+]

Progress for sure! HDMI

ok I found an easy way to do this configuration
from the terminal run
sudo raspi-config
that will change the screen to

hit the down arrow to Advanced Options and hit enter

hit the down arrow to Resolution

here you can try different modes to remove the input not supported

 

[DirtyRed07]

ok I found an easy way to do this configuration
from the terminal run
sudo raspi-config
that will change the screen to
View attachment 718143
hit the down arrow to Advanced Options and hit enter
View attachment 718144
hit the down arrow to Resolution
View attachment 718145
here you can try different modes to remove the input not supported

Fixed! Thanks for all the help, sorry if I was annoying!

 

[RandR+]

Fixed! Thanks for all the help, sorry if I was annoying!

Great! what was the setting that did the trick?

 

[DirtyRed07]

Great! what was the setting that did the trick?

1600x900 was highlighted, I clicked a different one, then back to 1600x900 then rebooted

 

[DirtyRed07]

At work and was wanting to mess around with my tap list but the host page won’t load. Internet is working fine for everything else. Any idea? Do I need to be on the same WiFi network?

 

[RandR+]

Any idea? Do I need to be on the same WiFi network?

you need to be on the same network or have a DNS listing to make your taplist ip public (i.e. anyone can find it) or have a VPN to your home network.


I have a router that has built in VPN access so I can use me phone to connect to my taplist if I want without making it public

also Im not sure the .local would work in either case you would need to type in the correct ip/address

 

[DirtyRed07]

you need to be on the same network or have a DNS listing to make your taplist ip public (i.e. anyone can find it) or have a VPN to your home network.


I have a router that has built in VPN access so I can use me phone to connect to my taplist if I want without making it public

also Im not sure the .local would work in either case you would need to type in the correct ip/address

Thanks, looks like I’ll just mess with it tomorrow since I have zero clue how to do any of that. Again, thanks for the help/info!

 

[day_trippr]

Unless there are multiple NAT'd levels you can be on any local network branch visible to your router and see your taplist.
As mentioned, once outside your LAN you need a port-forwarding rule and an external IP address for your primary router to see R'Pints from the world...

Cheers!