| anonym | Anmelden | Neues Konto anmelden | 2010-09-06 20:05 CEST |
| Startseite | Übersicht | Einträge anzeigen | Änderungsprotokoll | Roadmap | Dokumentation | Konto |
| einfache Eintragsansicht [ Zu Notizen wechseln ] | [ << ] [ >> ] | [ erweiterte Anzeige ] [ Eintrags-Historie ] [ Drucken ] | ||||||||||
| ID | Kategorie | Auswirkung | Reproduzierbar | Meldungsdatum | Letzte Aktualisierung | |||||||
| 0000011 | [phpSQLiteCMS] General | kleinerer Fehler | immer | 2009-10-19 20:15 | 2010-01-05 19:36 | |||||||
| Reporter | BillB | Anzeigestatus | öffentlich | |||||||||
| Bearbeitung durch | ||||||||||||
| Priorität | normal | Lösung | offen | |||||||||
| Status | Rückmeldung | Produktversion | 2.0 beta 1 | |||||||||
| Zusammenfassung | 0000011: Switching content_function to true causes evalation of [function:] inside of <pre> block | |||||||||||
| Beschreibung |
When I change the setting for content_function to true, the example on the documentation/advanced_configuration page evaluates instead of displays. Instead if producing; You can now specify function calls like this: [function:myFunction(2,3)] it shows: You can now specify function calls like this: 5 I tried putting it inside of <code> block, like so,<code>[function:myFunction(2,3)]</code> |
|||||||||||
| Zusätzliche Information | ||||||||||||
| Tags | Keine Tags zugeordnet. | |||||||||||
| Angehängte Dateien | ||||||||||||
|
|
||||||||||||
Notiz |
|
|
(0000044) BillB (Reporter) 2009-10-19 20:21 |
From BillB, I forgot to escape the \<pre\>\<code\> block in the description above. The example should have been in the correct form, same as in the following paragraph on page documentation/advanced_configuration. |
|
(0000083) Alex (Administrator) 2009-12-22 09:40 |
That's how it should be, shouldn't it? |
|
(0000084) BillB (Reporter) 2010-01-05 19:36 |
I would say that the \<pre\> shows an intention to talk about functions in code. If a string like "[function:myFunction(2,3)]" always gets evaluated, it becomes inexpressible in a simple phpSQLiteCMS page. There may be a way to escape the string but I haven't found a way to do it. Note that it doesn't get evaluated in the little include page function it wrote, so maybe that's a workaround. http://billbreitmayer.com/phpsqlitecms/ [^] ( bottom of page ) It's not a big issue in any case, especially in a CMS that works so well and has such a great feature set ! :-) |