Textpattern CMS support forum

You are not logged in. Register | Login | Help

#51 2017-12-30 20:50:02

Vienuolis
Member
From: Vilnius, Lithuania
Registered: 2009-06-14
Posts: 178
Website

Re: Hello Themes!

bici wrote #308503:

do you know which hosting provider has Hiawatha?

I would like to host Textpattern websites myself, but I do not know about big business hosting companies, sorry. Yet we might want to ask for them on Hiawatha forum.

But here were the suitable software listed, not hosting companies.

Offline

#52 2017-12-31 05:03:47

phiw13
Plugin Author
From: Japan
Registered: 2004-02-27
Posts: 1,677
Website

Re: Hello Themes!

Bloke wrote #308506:

I like Pete’s take on the requirements. Here’s my first stab at a rewrite. Comments / improvements welcome.

Looks fine, I think. Not too much pushing the latest and greatest, but still gently suggesting to stay up-to-date with the server stuff.

Offline

#53 2017-12-31 08:34:01

philwareham
Core designer
From: Farnham, Surrey, UK
Registered: 2009-06-11
Posts: 3,196
Website

Re: Hello Themes!

Thanks all. BTW I’d like to push minimum PHP version for Textpattern 4.8 to PHP 5.5 (a separate discussion) so we could tie in GraphQL support with custom fields/content. Hello enterprise-level features.

Offline

#54 2018-01-10 10:19:15

philwareham
Core designer
From: Farnham, Surrey, UK
Registered: 2009-06-11
Posts: 3,196
Website

Re: Hello Themes!

A question for Textpacks and Pophelps…

What should the wording be for the remove_extra_templates Textpack string? And a short explanation for the pophelp too please. If you can let me know, I can then finish the translation system updates.

Thanks!

Offline

#55 2018-01-10 10:55:28

Bloke
Developer
From: Leeds, UK
Registered: 2006-01-29
Posts: 8,672
Website

Re: Hello Themes!

What it really does is delete everything before it starts the import/export process. So, dunno. Something like this maybe:

  • Delete destination templates first?
  • Replace all templates in destination?

First stab at the pophelp. I’m sure it can be improved:

Check this box to irrevocably delete all Page, Form or Style theme assets in the destination before the import or export operation takes place. If you clear the checkbox, the templates in the destination area will be merged with whatever you are copying: any assets of the same name will be overwritten, but any assets of different names that are already there will remain.

During export to the file system, this does not affect files other than Pages, Forms and Stylesheets. Any additional assets you may have (JavaScript, images, …) in other directories inside your theme will remain, regardless of the setting of this checkbox.


The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.

Txp Builders – finely-crafted code, design and Txp

Offline

#56 2018-01-10 11:47:36

philwareham
Core designer
From: Farnham, Surrey, UK
Registered: 2009-06-11
Posts: 3,196
Website

Re: Hello Themes!

@bloke Ta!

Offline

#57 2018-01-10 12:00:49

jakob
Admin
From: Germany
Registered: 2005-01-20
Posts: 3,487
Website

Re: Hello Themes!

Further ideas:

  • Scrub (or wipe clean) template folder before import/export?
  • Remove (or clear out) leftover / stray / templates?

One question: how does this affect importing? Surely it can’t wipe the directory with your freshly-created theme files? Do you mean it clears out the undefined forms/templates in that theme in the database?

Possible edits:

Check this box to wipe clean the Page, Form and Style theme assets in the destination template before importing or exporting your theme’s Pages, Forms and Styles.

Leave unchecked to merge your template changes into the existing template directory. Assets of the same name will be overwritten, but any existing assets with other names will remain.

Note: this does not affect files other than Pages, Forms and Stylesheets. Any additional assets – such as JavaScript, images, or webfonts – in other directories inside your theme will remain.

If this is only really relevant to export, maybe leave out import to avoid confusion.


TXP Builders – finely-crafted code, design and txp

Offline

#58 2018-01-10 12:18:35

Bloke
Developer
From: Leeds, UK
Registered: 2006-01-29
Posts: 8,672
Website

Re: Hello Themes!

jakob wrote #308619:

how does this affect importing? Do you mean it clears out the undefined forms/templates in that theme in the database?

Checking the box during export will:

  • Completely remove ALL your pages/forms/styles from the selected theme(s) on disk.
  • Recreate them all from what’s in the database.
  • If any ‘essential’ assets are missing, they will be created in the file system (with empty content).

Checking the box during import will:

  • Completely remove ALL your pages/forms/styles from the selected theme(s) in the database.
  • Recreate them all from the copies on disk.
  • If any ‘essential’ assets are missing, they will be created in the database (with empty content).

It’s essentially “blat everything and make a clean copy” in whatever direction you choose.


The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.

Txp Builders – finely-crafted code, design and Txp

Offline

#59 2018-01-10 12:37:05

philwareham
Core designer
From: Farnham, Surrey, UK
Registered: 2009-06-11
Posts: 3,196
Website

Re: Hello Themes!

I’ve done the pophelp now based on Stef’s initial suggestion. Feel free to amend though if you want.

Offline

#60 2019-08-25 20:47:22

jakob
Admin
From: Germany
Registered: 2005-01-20
Posts: 3,487
Website

Re: Hello Themes!

Pat64 wrote #308446:

Except: any call to forms doesn’t work within such an ‘error_default’ page template.

Bloke wrote #308451:

Yes, that’ll probably fail for the same reason as the txp_die itself used to fail before I patched it: there’s no concept of “which theme” the system is using under error conditions.

Was there a solution to this? I’ve just come across the phenomenon of not-found forms in an error_503 page template when using Jukka’s updated version of rah_maintenance. This thread came up in my search. Oddly, the error_default page seems to work, so maybe the problem lies with rah_maintenance.

EDIT: rah_maintenance is so small (see here), it seems unlikely that the bug lies there. I may have been seeing different output because I was logged out on one window (to see the maintenance page) but on the other regular 404 error page, I was logged in.

FWIW, this is what the error_503 page shows a non-logged-in user:

general_error Notice: Undefined index: skin on line 5443

textpattern/plugins/rah_maintenance/rah_maintenance.php:64 txp_die()
textpattern/lib/txplib_misc.php:1986 Rah_Maintenance->errorPage()
textpattern/publish.php:206 callback_event()
index.php:107 include()

tag_error <txp:output_form form="html_head" /> ->  Textpattern Warning: output_form unknown_tag while_parsing_page_form: none, none

textpattern/lib/txplib_publish.php:524 trigger_error()
textpattern/lib/txplib_publish.php:429 processTags()
textpattern/lib/txplib_misc.php:5482 parse()

… and the same again for each form that is called using output_form. Any ideas?


TXP Builders – finely-crafted code, design and txp

Offline

Board footer

Powered by FluxBB