Loading...
 
Skip to main content

Steps to complete Wiki to Yes

Only tasks listed below with a GO will be invoiced!
Tasks that are finished (fixed) or cancelled will be stored at 00.at-ToDos-old

Missing tasks (from emails)

Steps after Update is finished

Video responsive size (youtube plugin)

The task I fixed was videos too small. Now the problem is they are not fitting to the size in smaller screens. Please add the task. It!s a Go.

You need to specify 2 classes. One for indicating this is a resoinsive ratio and one that set the ratio (1x1, 4x3, 16x9 or 21x9)
IE: "ratio ratio-16x9"

Fixed here: https://wiki-to-yes.org/Mediation
Please re-open if you want me to check all your page using the youtube plugin.

Status = Go (from 1/09/2023 email)
Completed = 30mn

Page action to buttons

See the screenshot please. I like to clean and optimize the footer area. The page action looks lost somehow. Thus I like them to appear next to the other buttons and same looking.

Proposals and estimation = 1h
Status = Please wait until this task is completed

No empty line above reading time

Proposals and estimation = 1h
Status =

code generated by the “backlink” plugin produce a list of items that are too close and too small for mobile. To be fixed with some code addition and css classes, to fix this add a task on the To-Do list.

Your status question is confusing. Please, be clear on what you want me to do. Is it a task or not ?
If it is, send me or attach a screenshot and the URL of a page demonstrating the issue

Estimate =
Status = Question: isn't that solved by the update where you adjusted CSS to bootstrap? Do we need to step into that since backlinks should not be visible for anonymous user? I like to postpone this task in case it is needed still.

Custom search in trackers

When searching words in tracker (i.e. Tracker IF 17) results are wrong. Items will not be found. The problem is described in https://wiki-to-yes.org/00.AT-Testsearch

Please don't mix cases on the same todo and on the same page it make things too complicate. Create seperate tasks for seperate cases, thanks.

Abga test case

If I enter "Abga" autocomplete offers "Abgabe" in dropdownlist. I click on it. "Abgabe" appears in searchfield as the term to look for. This is corect. But if I start the search, there are no results.

Work fine for me:

Status = Go
Completed = (studies and cleaning code) 30mn

Achtsamkeitsfokus test case

Your description was confusing. I understood that: when searching for "Achtsamkeit" the autocomplete list shows "Achtsamkeitsfokus" if you select it and seach there is no results.
On my test, when search using a customsearch tool with your template "Achtsamkeitsfokus" cannot be found.
I will try to reproduce locally to fix things.

Studies = 30mn
Status = Go
Completed =

Searching with letters like ä,ö,ü

Words including those letters will not be found.

Estimate = Pending (preliminary Custom search in trackers)
Status =

Tracker fiiltering multiselect fields

Entries i.e. in Tracker17 will not be found if there are two or more selections in a field. See https://wiki-to-yes.org/Technikenverzeichnis. For example: "Metakommunikation" should be found if I choose "Phase 3" in the dropdownfield.

Esitmate = Pending (preliminary Custom search in trackers)
Status =


Postponed or cancelled

I will check the status, before we go on with further tasks. I have aplan to change permissions and group structure and I am testing with digistore. I will tell my ideas and results as soon as I am more clear about.

Results in Google

Google alert finds only trackeritems not wiki pages and not articles or forum posts. What's wrong?

Estimate = Stalled (I need much more informations please give me details)
Status = Check and offer

Create a list of all who contributed to the site. (to motivate authors)

see mail of 28th February and mail with subject "Display the creator AND contributors of a wiki page". Set a customSearch to select which user we are looking for. There is a module "customLastContributorPages_bs" does it do the job? Once I saw you added a button in the profile. Could be enough at the first hit. Please use the profile userProfileSmall.tpl (next to edit button)

Estimate = Stalled - 30mn to 1h to review all the mails, what code was done, what is missing
Status = Results?

Pay per view content (Appearance and Look and Feel)

Initial request corrected

1. Using 2 different templates for Anonymous user and Premium user (premium user will have a small blue line under the menu)
2. Anonymous user do not see part of the content (IE:top area - where you find page ID, categories, page actions structured menu and so).
3. Premium user can access to "hidden" content per page if they want to see this part of the page or not.
See my mail from 21st of July subjected to Appearance and Look and Feel

Bernard answer, proposal

The mechanism above is, in my opinion, complex for little improvement.
It can be done the easy way (using CSS classes) but can be bypassed evenly easily. A complete solution require complex code and tweaking Tiki main layout mechanism. I suggested to use a commonly used solution, let the anonymous see the start of a page with a notice "To read the full content of this page subscribe..."
See my mail from 22/07/2023 subjected Wiki-to-yes - Monetize page content to enroll more subscribers

I use perspectives until we find better solution. See my mail subjected to "Pay per view content (Appearance and Look and Feel)" of 11th of August.

Proposals and estimation =
Status =

There are three issues regarding cookie consent:
1. Problem: Dialog avoids reading the data protection rules
2. Problem: some users want to use the page without cookies.
3. Problem: For data protection description what cookies precisely will be stored?

Estimate = 30mn to study your request and possible solutions (improvement were added in Tiki25)
Status = Cancelled

Forbiding access for non-admin to item123 urls, forbid Google from indexing them, having a pluginList alternative instead

Issue to solve: The tracker view for item is not the best and we want to improve it so existing users and visitors can be driven to different pages of the website.
Context: For years Google index anything he could found without control. We started to clean the mess and have Google to propose as results page that are good for wiki-to-yes business and goals. This task is about getting back under control the display of our public (anonymous can see) trackeritems.
Solution:

  • Hide what should not be seen
    • Disallow index for item*
    • Set permissions in a way only admins can see the tracker system view (users will see items through templates from List, CustomSearch and ListExecute)
  • Display items with a custom template
    • Setup prefix alias
    • Setup aliases
    • Create templates (one per public tracker)
    • Create and setup plugins to display items in our templates
    • Allow index of items through our prefix alias
    • Track and fix last item* still indexed at Google

Estimate = 8h to 10h
Status =

Premium access (membership with payments)

Manage Premium access including https://www.digistore24.com// purchase process, where VPN-calls inistiate the access and cancelling premium membership. See mails subjected to Wiki-to-yes - Premium access (membership with payments).

Estimate = On hold till tiki25 is up, Stalled (see my mail from the 28/05/2023), once first step is completed it is likely I'll hire external consultant.
Status = Go

LDAP access

Mr Sauer installed LDAP on the server where we store user data from members of the association "integrated Mediation" (www.in-mediation.eu). This might solve the problem how to incluse members of partner associations. Now LDAP access should be possible also. Those users should access premium membership directly. (Should be possible according to "Group membership and permissions" in https://doc.tiki.org/LDAP-authentication. Possible to make LDAP access available for those users as well?

Estimate = On hold till tiki25 is up, I can assist only someone that understand what it do and what you want. (too many unknowns in my opinion). If it doesn't work or more is expected than filling fields I'll hire external consultant.
Status = Check and offer

Finished

Upgrade to Tiki25

Tiki25 is out since 6 month and working just fine (I think wiki-to-yes is one of the last Tiki I have still in Tiki24). It include tons of improvement and prepare for bigger upgrade (Tiki will move soon to PHP8.1 and 8.2). The extra work will be the Bootstrap5 adaptation the rest should work without any adaptation.

  • Install and setup a Tiki25 test
  • Port Wiki-to-yes customization (theme, template, files)
  • Adapt the at-theme to bootstrap5
  • test it all
  • Publish Tiki25 as the main wiki-to-yes


Please check : https://test.wiki-to-yes.org/
Add here the issues you want me to fix:

Description (what you see / what is needed) URL / Page Estimate Status Remarks
Menu CSS: Anchor, Items spacing, dropdown spacing and positionnig. (email 28/06/2023) https://wiki-to-yes.org 1h (max) ... ...
Menu Smartmenus: Submenus arrows on each sub items. (email 28/06/2023) https://wiki-to-yes.org 1h (max) ... ...
Cookies consent: I can go on without checking the option „I accept cookies“ https://test.wiki-to-yes.org/tiki-admin.php?page=login 15mn Fixed See:
Change slider not needed

Change slider for swiper or carousel. (email 28/06/2023) | https://wiki-to-yes.org/Abteilungen-Slider | 1h (studies) | ... | Manual slider (each slide is a set with name and URL) and to be included on other pages... It requires test and evaluation. Ideally all the pictures should be in the same file gallery with a naming and the description could be used as URL.

I managed here: https://wiki-to-yes.org/Start

Bottom button floating issue. (email 28/06/2023) https://test.wiki-to-yes.org/Wissensgrundlagen 15mn Fixed I applied the change and it seems ok to me (positionning may be ?)



^
Completed =

  • 2h to create a new 25.x branch on dev (install, porting database, files, custom files and publishing)
  • 2h (at-theme for bootstrap5)
  • 2h menu, logo, module menu, spacing, link colors, buttons, breadcrumb and admin colors fixes (dark and light) (else the site would have been very hardly to use)


Estimated =

  • 2h turning off the 24.x version and setting the new 25.x version (install, porting database, files, custom files and publishing)


Status = GO