Helpdocs editing from ACP doesnt work

[Serious]

So i got mybb 1.8.24 with duende template.

At the top there is a button "HELP" wich leads me to help section. 
Section consists of a page with categiries and documents inside those categories. simple.

I go to ACP to Configuration -> Help Documentation. I can make new categories, add documents under those categories but on frontend NOTHING CHANGES... nothing at all. So i open up /inc/languages/*mylanguage*/helpsections.lang.php and helpdocs.lang.php and they are default.. no changes made in them. 

So if i edit these files - i see changes at frontend that i made in filed. BUT only if i change sections and doc given in files. I cannot create new sections and docs in old sections and in new too. They dont apper on front end and in ACP no changes. Lts like ACP is not connected to front end help page and to these files.  I mean am i the only one experiencing this issue? 

Thanks in advance..

[nixer55]

You're not alone.  Can see the ACP edits in the database, but mybb's reading them from the php files.  Last time I checked anyway.

Used to edit help custom for our board.  Overwritten every upgrade, so gave it up.

[wingedcatgirl]

This issue only seems to affect the default built in help documents, so we worked around it by copying their contents into new documents and deleting the originals.

[nixer55]

This issue only seems to affect the default built in help documents, so we worked around it by copying their contents into new documents and deleting the originals.

That seems to work!  How odd! 

But doesn't seem to work for new docs.  So limited in functionality.

[censor_deeznutz]

This issue only seems to affect the default built in help documents, so we worked around it by copying their contents into new documents and deleting the originals.

That seems to work!  How odd! 

But doesn't seem to work for new docs.  So limited in functionality.

Yep, for now the three workarounds until such issue is sorted out seem to be for 1) existing help documents, edit via the respective lang files *though such would be overwritten on any core update & or 2) as noted above: copying the default contents into new documents and deleting the originals, though personally haven't tried this method

AND the third workaround is most likely what folks want to get the dbs functionality back:  you can force it to pull your changes from dbs rather than pull from lang file by running these two sql updates to respective in phpmyadmin:

UPDATE `mybb_helpsections` SET `usetranslation` = '0';

UPDATE `mybb_helpdocs` SET `usetranslation` = '0';

[nixer55]

Yep, for now the three workarounds until such issue is sorted out seem to be for 1) existing help documents, edit via the respective lang files *though such would be overwritten on any core update & or 2) as noted above: copying the default contents into new documents and deleting the originals, though personally haven't tried this method

AND the third workaround is most likely what folks want to get the dbs functionality back:  you can force it to pull your changes from dbs rather than pull from lang file by running these two sql updates to respective in phpmyadmin:

UPDATE `mybb_helpsections` SET `usetranslation` = '0';

UPDATE `mybb_helpdocs` SET `usetranslation` = '0';

Thanks, I'll try that in my test system and report back.

[censor_deeznutz]

Yep, for now the three workarounds until such issue is sorted out seem to be for 1) existing help documents, edit via the respective lang files *though such would be overwritten on any core update & or 2) as noted above: copying the default contents into new documents and deleting the originals, though personally haven't tried this method

AND the third workaround is most likely what folks want to get the dbs functionality back:  you can force it to pull your changes from dbs rather than pull from lang file by running these two sql updates to respective in phpmyadmin:

UPDATE `mybb_helpsections` SET `usetranslation` = '0';

UPDATE `mybb_helpdocs` SET `usetranslation` = '0';

Thanks, I'll try that in my test system and report back.

Yeah, that only dawned on me on a quick glance at the 5 usages of 'usetranslation' in misc over a quick sip of coffee while considering another thread topic that would be affected by same issue and not wanting to dig around at the moment I was like, hmm, wait why not just set 'usetranslation' to '0' rather than '1' for both sections and docs until an actual official solution is provided, as the desire is to use the acp input method for doc editing that is not necessarily reliant on defined translations if one really thinks about the fact that the doc input edit is user defined on submittal & not lang file defined unless say said edit was writing to a writable lang file rather than dbs insertion, haha and well, yep, setting 'usetranslation' to such 'off' position made my edit from acp default help doc edit display in frontend hence the suggestion shared here

[nixer55]

Works for me in test.  No reason to think it won't live.

cheers...

[censor_deeznutz]

Works for me in test.  No reason to think it won't live.

cheers...

cool beans and no worries!