Search
Items tagged with: bugResearch
Can you pin the following bug research info layout on the helpers page?
That way people get a better idea what is needed of info to adress their queries.
Also, if we could add a spoiler with the respective prepared markdown code, people can use it to post on github their report.
Click to open/close
#bugResearch
[spoiler=Platform Info: friendica VERSION]Friendica Version: (you find this information on your server at https://yourfriendicanode.com/VERSION
Friendica Source: ( most likely gitHub)
PHP version: (if this is relevant information ask you admin in any case)
SQL version: (if this is relevant information ask you admin in any case)
memory_limit: (if this is relevant information ask you admin in any case)
resources: (?X) Core CPU, (?) GB Ram with (?)GB Disk
[/spoiler][hr]I [b]did/n't[/b] have a look at gitHub
[spoiler=Short bug description:]Overall summary of the issue.
Replace the texts inside this and the following spoilers with your description.[/spoiler][spoiler=Details of the buggy behavior:][url=https://forum.friendi.ca/display/]Link to the respective friendica helpers forum page discussion if there is.[/url]
Try to explain in short sentences and with precise wording what happens.[/spoiler][spoiler=¿Possible to reproduce, if so how:]step one to reproduce the problem
step two
step three[/spoiler][spoiler=Expected result:]¿what should be the correct behavior?
¿what did you expect?[/spoiler][spoiler=Screenshots:][img=]the better and dedicated the screenshot and the info involved the better[/img]
[img=]don't include unnecessary or compromising details in the screenshot[/img][/spoiler][hr]information for dev and server team:[spoiler=php.error.log]LEAVE THIS AS IS, the server team will use this report if possible/necessary[/spoiler]how the bug report actually looks like:
#bugResearchPlatform Info: friendica VERSION
Friendica Version: (you find this information on your server at https://yourfriendicanode.com/VERSIONFriendica Source: ( most likely gitHub)
PHP version: (if this is relevant information ask you admin in any case)
SQL version: (if this is relevant information ask you admin in any case)
memory_limit: (if this is relevant information ask you admin in any case)
resources: (?X) Core CPU, (?) GB Ram with (?)GB Disk
I did/n't have a look at gitHub
Short bug description:
Overall summary of the issue.Replace the texts inside this and the following spoilers with your description.
Details of the buggy behavior:
Link to the respective friendica helpers forum page discussion if there is.Try to explain in short sentences and with precise wording what happens.
¿Possible to reproduce, if so how:
step one to reproduce the problemstep two
step three
Expected result:
¿what should be the correct behavior?¿what did you expect?
Screenshots:
Information for dev and server team:
php.error.log
LEAVE THIS AS IS, the server team will use this report if possible/necessary
Cătă wrote:
I don't think there is a version problem
Here you find this same post but on friendica 2021.01, it displays the same than over here. I saw Michael Vogel state that friendica transmits html so I guess this applies here to.
Even than, at some point this "issue" appeared, maybe when markdown was added, so from the publishing stand point there is a version this issue started.
This profile hasn't markdown enabled.
If the issue is because of markdown it's still a bug in my opinion.
Please correct me if I'm wrong but I guess we are also witnessing an error in the /help page discription, as it is [*] instead of [li], isn't it? If so this is also something for to mention or directly fix in the github repo I think.
If you go to github, I'm working on a bug report layout maybe it suits you (attention, this is bbcode!):
Click to open/close
#bugResearch
[spoiler=Platform Info: friendica VERSION]Friendica Version: (you find this information on your server at https://yourfriendicanode.com/VERSION
Friendica Source: ( most likely gitHub)
PHP version: (if this is relevant information ask you admin in any case)
SQL version: (if this is relevant information ask you admin in any case)
memory_limit: (if this is relevant information ask you admin in any case)
resources: (?X) Core CPU, (?) GB Ram with (?)GB Disk
[/spoiler][hr]I [b]did/n't[/b] have a look at gitHub
[spoiler=Short bug description:]Overall summary of the issue.
Replace the texts inside this and the following spoilers with your description.[/spoiler][spoiler=Details of the buggy behavior:][url=https://forum.friendi.ca/display/]Link to the respective friendica helpers forum page discussion if there is.[/url]
Try to explain in short sentences and with precise wording what happens.[/spoiler][spoiler=¿Possible to reproduce, if so how:]step one to reproduce the problem
step two
step three[/spoiler][spoiler=Expected result:]¿what should be the correct behavior?
¿what did you expect?[/spoiler][spoiler=Screenshots:][img=]the better and dedicated the screenshot and the info involved the better[/img]
[img=]don't include unnecessary or compromising details in the screenshot[/img][/spoiler][hr]information for dev and server team:[spoiler=php.error.log]LEAVE THIS AS IS, the server team will use this report if possible/necessary[/spoiler]how the bug report actually looks like:
#bugResearchPlatform Info: friendica VERSION
Friendica Version: (you find this information on your server at https://yourfriendicanode.com/VERSIONFriendica Source: ( most likely gitHub)
PHP version: (if this is relevant information ask you admin in any case)
SQL version: (if this is relevant information ask you admin in any case)
memory_limit: (if this is relevant information ask you admin in any case)
resources: (?X) Core CPU, (?) GB Ram with (?)GB Disk
I did/n't have a look at gitHub
Short bug description:
Overall summary of the issue.Replace the texts inside this and the following spoilers with your description.
Details of the buggy behavior:
Link to the respective friendica helpers forum page discussion if there is.Try to explain in short sentences and with precise wording what happens.
¿Possible to reproduce, if so how:
step one to reproduce the problemstep two
step three
Expected result:
¿what should be the correct behavior?¿what did you expect?
Screenshots:
Information for dev and server team:
php.error.log
LEAVE THIS AS IS, the server team will use this report if possible/necessary
@Friendica Support
Hi there.
As the new friendica stable version has come out recently and apparently there aren't mayor problems with the updates I wanted to ask you to consider some suggestions about the helpers/coders/admins etc pp setup we have on forum.friendi.ca
In general terms speaking when ever someone comes up with some bug report or feature request some comment show up saying "go to github and ..".
There are several reasons I consider this is not to helpful and that we should find at least some work around. First of all we all know and are aware by whom github is owned and that there are more than one of us out here who don't like to go to that site for that very reason. At the same time it is where the coding community is, where cross over communication between the fedeVerse platforms can happen and where in any case recruitment and help request for none friendica specific issues can be found or can be published. So even as we have git.friendi.ca as a a very important back up plan and backup tool it most likely will not become part of our production scheme in the near future.
Than there is the friendica community itself, a whole lot of people that are using friendica and have access to the forum.friendi.ca server with the few forum pages that do exist as of now. These are people that might not be skilled in coding itself but could do bug research, publish bug reports, have feature requests or ideas, could help out with standard helpers Q&A or even translation hints or pointing out missing translations.
I do guess that we might have more than one community member out there that is not available to sign up to another site like github or transifex (I guess that's still our translation site?) but would help out if we'd had some more forumpages like @bugresearch, @tutorial, @featureRequests. I could envision even people who love to dedicate some time to administer a forumpage like @tutorial that once some text has been created by the community in such a forum could republish such a text from that very forum page sorting that text into a given category of that forumpage.
Like to say, there is lot's of information that get's discussed or explained and than just "goes down the drain" and get's lost in the stream instead of being pushed into some category of the helpers page where it could be found easily by others.
A bugResearch forumpage for example could have a pinned post containing a bug research template like the following so people could post there findings in the first place and every once in a while someone who does have a github account and signs "responsible" to port those reports to github simple copy-pastes those reports to github with a link to the respective forum post.
Example bug research template for a @bugResearch froumPage on forum.friendi.ca:
#bugResearch
Platform Info: 2023.05 - old stable | VIER | firefox
Friendica Version: 2023.05 - old stableTheme: VIER
Browser: firefox
Friendica Source: gitHub
PHP version: 8.1.2-1ubuntu2.14
SQL version: MySQL / MariaDB
memory_limit 256M
4 Core CPU, 8 GB Ram with 300GB NVME Disk
I did/n't have a look at gitHub
Short bug description:
Overall summary of the issue.Replace the texts inside this and the following spoilers with your description.
Details of the buggy behavior:
Try to explain in short sentences and with precise wording what happens.¿Possible to reproduce, if so how:
step one to reproduce the problemstep two
step three
Expected result:
¿what should be the correct behavior?¿what did you expect?
Screenshots:
information for dev and server team:
php.error.log
LEAVE THIS AS IS, the server team will use this report if possible/necessary---------------------------------------------------------------------------
code of this example bug report
#bugResearch
[spoiler=Platform Info: 2023.05 - old stable | VIER | firefox]Friendica Version: 2023.05 - old stable
Theme: VIER
Browser: firefox
Friendica Source: gitHub
PHP version: 8.1.2-1ubuntu2.14
SQL version: MySQL / MariaDB
memory_limit 256M
4 Core CPU, 8 GB Ram with 300GB NVME Disk[/spoiler]
I [b]did/n't[/b] have a look at gitHub
[spoiler=Short bug description:]Overall summary of the issue.
Replace the texts inside this and the following spoilers with your description.
[/spoiler]
[spoiler=Details of the buggy behavior:]Try to explain in short sentences and with precise wording what happens.[/spoiler]
[spoiler=¿Possible to reproduce, if so how:]step one to reproduce the problem
step two
step three
[/spoiler]
[spoiler=Expected result:]¿what should be the correct behavior?
¿what did you expect?[/spoiler]
[spoiler=Screenshots:]
[img=]the better and dedicated the screenshot and the info involved the better[/img]
[img=]don't include unnecessary or compromising details in the screenshot[/img][/spoiler]
[hr][hr]
information for dev and server team:
[spoiler=php.error.log]LEAVE THIS AS IS, the server team will use this report if possible/necessary[/spoiler]
Can't publish public when mentioning forum pages
@Friendica Support
Hi there,
not sure if this is a bug or just that I'm missing some idea/rule functionality.
Platform Info: 2023.05 - stable | VIER | firefox
Friendica Version: 2023.05 - stableTheme: VIER
Browser: firefox
Friendica Source: gitHub
PHP version: 8.1.2-1ubuntu2.14
SQL version: MySQL / MariaDB
memory_limit 256M
4 Core CPU, 8 GB Ram with 300GB NVME Disk
I didn't have a look at gitHub
Short bug description:
When I try to publish publicly a post addressing two forum pages of this server, gimped and tutorial (tutorial is an account created with this profile), I get a restricted post and I don't understand why.Details of the buggy behavior:
I publish the post as public but it gets displayed as private, only visible for the forum page gimped that actually figures twice in the information card of the lock icon.Also, I can't pin the post to my profile.
See image gif in screenshots spoiler
¿Possible to reproduce, if so how:
This is the code of the post, it happens every time I try:(somehow friendica alters the tags in this code)
#newHere #neuHier #hola
[img=https://fika.grin.hu/photo/media/411601]Gif scene of the movie "The Martian".
The lonely main actor is sitting on a stone on the inhabited planet he was left on alone.
A text reads:
"First day in the diaspora of the fediVerse .."
The astronaut is depicted how he opens the solar panels of his equipment, presses a big button on it and the hashtags #hola, #neuHier and #newHere appear.
In the last scene he sits again on his stone and the text: ".. wait .." is displayed.
In the first scene that reads the text about the first day in the fediVerse the probably oldest logo of the fediVerse is displayed at the bottom left of the scene. At the horizon on the right the actual logo of the the fediVerse rises behind the landscape.
In the last scene, while our hero is awaiting the outcome of his intent to make contact with the outside world, the old Federated Social Web logo appears in front of the sun.[/img]
#[url=https://tupambae.org/search?tag=fediVerse]fediVerse[/url] #[url=https://tupambae.org/search?tag=fediHelp]fediHelp[/url] #[url=https://tupambae.org/search?tag=fediTips]fediTips[/url] #[url=https://tupambae.org/search?tag=gimp]gimp[/url] #[url=https://tupambae.org/search?tag=gimped]gimped[/url]
@ gimped@tupambae.org @[url=https://tupambae.org/profile/tutorial]Tutorial[/url]Expected result:
¿what should be the correct behavior?¿what did you expect?
Being posted public, shared by the forum pages publicly and being able to pin it to my profile.
Screenshots:
PHP error log thrown in /src/Database/Database.php on line 191
hi there, I have this message in my php.error.log
what should I do?
I didn't have a look at gitHub
php.error.log Database.php on line 191
thrown in /var/www/html/src/Database/Database.php on line 191[14-Nov-2023 14:15:30 UTC] PHP Fatal error: Uncaught mysqli_sql_exception: Connection refused in /var/www/html/src/Database/Database.php:191
Stack trace:
#0 /var/www/html/src/Database/Database.php(191): mysqli->__construct()
#1 /var/www/html/src/Database/Database.php(97): Friendica\Database\Database->connect()
#2 [internal function]: Friendica\Database\Database->__construct()
#3 /var/www/html/vendor/level-2/dice/Dice.php(132): ReflectionMethod->invokeArgs()
#4 /var/www/html/vendor/level-2/dice/Dice.php(96): Dice\Dice->Dice\{closure}()
#5 /var/www/html/src/DI.php(98): Dice\Dice->create()
#6 /var/www/html/src/DI.php(66): Friendica\DI::dba()
#7 /var/www/html/src/DI.php(54): Friendica\DI::setCompositeRootDependencyByHand()
#8 /var/www/html/index.php(35): Friendica\DI::init()
#9 {main}
thrown in /var/www/html/src/Database/Database.php on line 191
Platform Info: 2023.05 - stable
Friendica Version: 2023.05 - stableFriendica Source: gitHub
PHP version: 8.1.2-1ubuntu2.14
SQL version: MySQL / MariaDB
memory_limit 256M
4 Core CPU, 8 GB Ram with 300GB NVME Disk