flat scripts in 4.7.2

colak · 2018-12-27 19:14:51

i see ^^. Intelligent foresight!

I gave the form an html media type and it works according to the label. I wish we had a how-to in the docs explaining all these. The docs and tips websites are great for tag basics and more advanced tag manipulation examples, but we have nowhere else but the forum to document these wonderful features.

I am by no means complaining. I’m just thinking aloud about the possibility of adding a section in the docs but I’m not sure if there will be enough interest from the people here to start a collaborative writing effort to make the docs site a more complete reference destination.

Bloke · 2018-12-27 21:08:37

colak wrote #315784:

I’m not sure if there will be enough interest from the people here to start a collaborative writing effort to make the docs site a more complete reference destination.

I’m interested!

We need to document this stuff, curate the good tips and examples from the forums and put them in the official docs wherever makes most sense. So if you spot any cool examples or tidbits of info that could help, collect them and propose changes either directly committing to the pages if you can, or raise them as issues and then we can fold them into the docs.

colak · 2018-12-28 08:56:50

Hi Stef, Unlike tags though this tip is about functionality. I guess that it could be added to FAQ but as features are becoming somewhat cryptic (see Example 8 I added a few weeks ago), the FAQ are becoming slightly irrelevant.

Thinking aloud again

What I would like to see developing is a user manual, presenting screen-shots of the installation process (starting with (s)ftp) to the use of tags when designing complex non blog and gallery sites. At the moment the vanilla front end template is excellent for blogs but it does not demonstrate the power and flexibility of txp as a CMS.

Furthermore, as txp is now and for some time has been a mature software, a tutorial on migrating large sites should also be included. Over 3 and a half years ago, I posted this one on textpattern.tips, but maybe a more generic version is needed.

In addition to the above chapters could include

Migrating a site from another blog system to txp (wp, joomla, etc)
txp concept basics (this could be a basic tutorial linking to the tag reference)
A step by step tutorial on the multi-site functionality (admittedly I have not used this as I still have no idea about what to expect)
Creating plugins (there is some documentation on this but is it up to date?)
Creating short-codes (There are numerous examples in the forum which I could collect, collate and sanitise).

All the above (except the plugin creation) should be geared for designers and hobbyists as I believe that it is the userbase we need to target for.

Bloke · 2018-12-28 09:50:56

That’s all good stuff, colak.

I’m on board with all of that except the screenshots. I’m of the opinion that screenshots create a rod for our backs because they become out of date faster than words, and the type of users whom they serve (mainly newbies) who might feel comforted by their use then end up feeling uncomfortable because the screenshot doesn’t match the reality.

Let’s figure out how to structure the docs to add the kind of stuff you mention.

Last edited by Bloke (2018-12-28 16:52:46)

jakob · 2018-12-28 11:09:25

colak wrote #315790:

What I would like to see developing is a user manual, presenting screen-shots of the installation process (starting with (s)ftp) to the use of tags when designing complex non blog and gallery sites. At the moment the vanilla front end template is excellent for blogs but it does not demonstrate the power and flexibility of txp as a CMS.

I agree wholeheartedly. I understand, too, that screenshots are hard to maintain but they are undoubtedly a great help for beginners. I know that when I look at other systems, screenshots help me get a handle on what to expect.

In general, I think we could split some of these things across the docs, tips and maybe even mag articles, as some are more examples than reference. Splitting things does, of course, add to the management requirement. There may be potential for a mag issue as quite a bit is new. I thought this might be a good txp-meet-up topic to discuss.

Migrating a site from another blog system to txp (wp, joomla, etc)

Without an import mechanism/format, this is, I think, very much a manual activity at the moment. The old importers worked while the other systems were still very basic. If you have access to the previous system and can control its output or massage its database, you can automate some of that. Building a site from an HTML template is, however, a relevant topic.

txp concept basics (this could be a basic tutorial linking to the tag reference)

I looked for this a few months back and even went as far as looking up Destry’s ‘seminal’ building-blocks articles on the way-back-machine. Things have changed a little since then, though.

A step by step tutorial on the multi-site functionality (admittedly I have not used this as I still have no idea about what to expect)

There are my multi-site installation instructions which must give you a pretty good idea and begin with “Why use a multi-site installation?”.

Creating plugins (there is some documentation on this but is it up to date?)

There are these which are, I believe, relatively up to date.

Creating short-codes (There are numerous examples in the forum which I could collect, collate and sanitise).

There are the docs and some examples in the docs, but I could also imagine examples being great as a category of the textpattern.tips site.

All the above (except the plugin creation) should be geared for designers and hobbyists as I believe that it is the userbase we need to target.

I also agree. The usage / getting started docs are for beginners, the rest should aimed at those with some knowledge of html and making websites.

Bloke · 2018-12-28 16:42:05

With regards screenshots (I was rushing when I wrote that, sorry) I should qualify that they should be used sparingly rather than as a matter of course. They do have value!

colak · 2018-12-28 17:45:28

Sorry I did not respond. I wanted to read the links posted.

I still have many questions re docs.textpattern.com/installation/multi-site-textpattern. ie

the creation of subdomain

So, the multi-site install can not serve different domains? Further down the tutorial says we can, but this is slightly confusing.

the unpacked file tree to the web root on your webserver

If the above is correct, would the web root be the one where the www domain is served from?

If you chose a database prefix and are using one database for several Textpattern installations, remember to enter it during configuration.

Does this mean that we can have different site designs, sections, categories, url schemas, articles, images, content in general, using just one install?

Also what about migrating multiple sites to multisite administration?

There are the docs and some examples in the docs, but I could also imagine examples being great as a category of the textpattern.tips site.

I have created a short-tags category in the textpattern.tips site, waiting to be populated. I’ll start collecting first.

colak · 2018-12-28 19:11:51

OK, I have created a short-tags category and written an article on the tips site (currently in drafts). One of the reasons I did not publish it is because textile does not seem to be parsing the tags starting with bc..

Julian, I understand you have publisher rights there, could you take a look?

This issue with textile seems to be appearing just for me and Stef:)

jakob · 2018-12-29 09:33:34

colak wrote #315803:

I still have many questions re docs.textpattern.com/installation/multi-site-textpattern. ie

Thanks for the feedback. I may go back and improve on it.

So, the multi-site install can not serve different domains? Further down the tutorial says we can, but this is slightly confusing.

Each site can be a different domain. It could also be a subdomain if you want it. The subdomain requirement refers to the admin and public sides: if they share the same domain, txp’s logged-in cookie works on the public and admin side together, which is useful for maintenance mode plugins or front-page edit links when logged in. So you could have the following structure:

/htdocs
    /sites
        /neme
            /admin      ->    admin.neme.org
            /private
            /public     ->    www.neme.org
        /neme-imca
            /admin      ->    admin.neme-imca.org
            /private
            /public     ->    www.neme-imca.org
        /neme-eventspace
            /admin      ->    eventadmin.neme.org
            /private
            /public     ->    eventspace.neme.org
        /statemachines
            /admin      ->    admin.statemachines.eu
            /private
            /public     ->    www.statemachines.eu
        /hblack
            /admin      ->    admin.hblack.net
            /private
            /public     ->    www.hblack.net
    /textpattern

If running multiple subdomains, as in the example with the eventspace subdomain, each admin area requires a separate subdomain, but you can name it how you like. I called it eventadmin. but you could also call it contributors. or manage. or whatever…

If the above is correct, would the web root be the one where the www domain is served from?

In this case I meant the folder on your host which is the base of your (theoretically) web-reachable folders. Many hosts call that www or htdocs with your account id-number. For a multi-site installation, you point your www.domain.com to the respective site’s public folder and the admin.domain.com to the respective site’s admin folder as in the example above.

Does this mean that we can have different site designs, sections, categories, url schemas, articles, images, content in general, using just one install?

Yes. Each site has its own admin area and own database (or database prefix) as before, but you have just one /textpattern folder with the files within it. The articles, images, links, categories are not all mixed up together in the same admin area.

Also what about migrating multiple sites to multisite administration?

There’s not an automated method, but it needn’t be complicated. Essentially, the /images, /files, /themes and any assets folders go into the /public folder, the config.php goes into the /private folder and if you’re using a plugin folder, put that in the /admin folder and adjust the paths accordingly in your site’s prefs. Likewise, the path in config.php needs adapting. Perhaps I should write another docs for that.

If you’re not averse to setting your own symlinks, you can theoretically also share content across multiple sites. When I was using rah_flat in the previous version of Textpattern, I had a /libs folder containing subfolders for sass modules, common javascript and also forms that were used in all the sites. That’s no longer quite as straightforward with the /themes folder.

jakob · 2018-12-29 11:41:33

colak wrote #315806:

OK, I have created a short-tags category and written an article on the tips site (currently in drafts). One of the reasons I did not publish it is because textile does not seem to be parsing the tags starting with bc..

Julian, I understand you have publisher rights there, could you take a look?

This issue with textile seems to be appearing just for me and Stef:)

I checked your article and all you were missing was a space after bc... As a result it output the actual code on the next line (adding an audio element) instead of showing the code. I added a space and brought it up to the same line and it shows fine now.

BTW: the method

bc..{space}
txp
… txp code example …

that we can use in the forum doesn’t work in Textpattern itself and seems to be something specific to the forum.

colak · 2018-12-29 14:12:08

!!! That was exactly what I needed to understand multi-site functionality. Thanks so much Julian… and also thanks re the tips. Of course I know about the spaces etc but it does not matter how much I was trying, the code would not render as a preformatted code.

Now… Back to the issue of the docs:)

Much of the new tag parser provides a lot of shortcuts which may not be very obvious. Up to 4.6.x, txp tags followed the xml type schema but since 4.7 and thanks to Oleg’s efforts, some of the syntax is not always fully understandable to designers. Further to example 8, I added to the docs a few weeks ago, and pointed out yesterday in this thread is based on Oleg’s forum post, makes no sense to me, but I know that it works. Like with the doc types or the new <header> functionalities, or even this very handy tip from Oleg (<txp:evaluate query='0<txp:variable name="no" />+1' />) which also works but I do not understand:)

Again, I am not complaining, I’m just excited by the possibilities and I’m trying to see how they can be made more accessible to designers.

bici · 2018-12-29 18:58:39

i hope this is where i post this question. In the new year i am going to finally give TxP and editing Flat Files a go. So what do i need to download/install to get started?

Textpattern CMS

Textpattern CMS support forum

#13 2018-12-27 19:14:51

Re: flat scripts in 4.7.2

#14 2018-12-27 21:08:37

Re: flat scripts in 4.7.2

colak wrote #315784:

#15 2018-12-28 08:56:50

Re: flat scripts in 4.7.2

#16 2018-12-28 09:50:56

Re: flat scripts in 4.7.2

#17 2018-12-28 11:09:25

Re: flat scripts in 4.7.2

colak wrote #315790:

#18 2018-12-28 16:42:05

Re: flat scripts in 4.7.2

#19 2018-12-28 17:45:28

Re: flat scripts in 4.7.2

#20 2018-12-28 19:11:51

Re: flat scripts in 4.7.2

#21 2018-12-29 09:33:34

Re: flat scripts in 4.7.2

colak wrote #315803:

#22 2018-12-29 11:41:33

Re: flat scripts in 4.7.2

colak wrote #315806:

#23 2018-12-29 14:12:08

Re: flat scripts in 4.7.2

#24 2018-12-29 18:58:39

Re: flat scripts in 4.7.2

Board footer