4.6 cannot create new forms

colak · 2016-10-08 17:16:41

I’m still experimenting on 4.6 and I’ve just hit another wall. I can not create new forms, css or js (using spf_js).

The process:

Create new form
give it a name
form type
content
click save

The page reloads with all the form fields empty and the name of the form does not appear on the left menu. Same happens with css and js.

I found a way around it which is to douplicate an existing form and edit the fields. This of course works for the css.

relevant diagnostics

Textpattern version: 4.6.0 (86d82f868a753eb919f2250d82f4dcae)
Last update: 2016-09-11 06:54:23/2016-10-02 05:41:36
PHP version: 5.6.26
GD Graphics Library: bundled (2.1.0 compatible); supported formats: GIF, JPG, PNG.
Server TZ: UTC
Server local time: 2016-10-08 17:13:43
Daylight Saving Time enabled?: 0
Automatically adjust Daylight Saving Time setting?: 0
Time zone: Asia/Nicosia (7200)
MySQL: 5.5.32-cll-lve
db_server_time: 2016-10-08 17:13:43
db_server_timeoffset: 1 s
db_global_timezone: SYSTEM
db_session_timezone: SYSTEM
Locale: en_GB.UTF-8
Server: Apache
PHP server API: cgi-fcgi
RFC 2616 headers: 0
Server OS: Linux 2.6.32-673.8.1.lve1.4.3.1.el6.x86_64
Active plugins: zem_contact_lang-4.0.3.6, act_if_mobile-0.1.2m, glx_if-0.7m, wet_slimpattern-0.4.1m, fha_time_diff-0.23m, zem_redirect-1.2.1, zem_contact_reborn-4.0.3.20, pap_contact_cleaner-0.1, mdn_count-1.4m, rvm_privileged-0.5, adi_mobile-0.2, pat_speeder-0.7.3, abc_feed-0.1, smd_wrap-0.20, smd_if-0.91, ike_slideshow-0.02m, rss_admin_db_manager-4.3, rah_external_output-1.0.4, rvm_css-1.1, spf_js-0.51, kuo_file_stats-0.1, adi_matrix-2.1beta2, smd_macro-0.30, smd_lib-0.36, smd_where_used-0.2, adi_notes-1.3.1, adi_search_db-0.3, ied_plugin_composer-1.1.0, rah_sitemap-1.3.0
Admin-side theme: hive 4.6.0

Pre-flight check:
————————————
New Textpattern version 4.6.1 available for download.
————————————

Bloke · 2016-10-08 18:21:20

I can’t repeat this on my test installation. What’s the outcome if you disable some/all of the plugins? Especially some of the older admin-side ones like spf_js that may not hook into the admin side in optimum ways.

If it turns out to be a plugin and you could narrow it down to one or two culprits, we could highlight the info on the non-working plugins thread.

colak · 2016-10-08 19:55:31

Thanks Stef, I was just about to to that, when I stabled against another little problem. Previously whenever I did such tests I would print the plugins page into a pdf so as to have a reminder of the enabled plugins. On 4.6 my pdf only has one page with 8 plugins visible in a page where over 40 are listed (many disabled of course). I tried to save the source of the page as an html file but interestingly the activecolumn is empty. Possibly because it is populated by js. I checked the css and I did not find a media="print" so I’m investigating that issue too. Having said that, I know that the enabled plugins are listed in the diagnostics.

The problem seem to have been temporary (3-4 hours). I disabled all plugins and re-enabled them one by one, saving a new form each time, now all is fine except i get two javascript links under presentation>menu. I’ll post that of course in the relevant thread.

Bloke · 2016-10-08 22:39:37

colak wrote #302044:

I would print the plugins page into a pdf so as to have a reminder of the enabled plugins. On 4.6 my pdf only has one page

Well now that is weird. I reproduced this. Happens on the Articles panel too. I set mine to view 100 per page and printed it to PDF: one page only. I repeated this on a 4.5.7 install and it printed all pages. Gotta be some CSS or something weird with the themes; it does it on all three admin themes.

Maybe Phil can shed some light on this.

uli · 2016-10-08 23:39:29

Firefox seems to choke on printing flex elements. Deactivating all flex attributes on body, main and div.txp-layout makes the full page print to PDF.

Edited to add: Yiannis, wet_plugout remembers all plugins’ states for you and re-activates them after testing. Link is in my signature.

Last edited by uli (2016-10-08 23:41:23)

phiw13 · 2016-10-09 02:32:33

uli wrote #302047:

Firefox seems to choke on printing flex elements.

And I think Firefox is actually doing that correctly (per spec). Although, historically, Firefox has always had problems (bugs) with printing large non-in-flow block elements. My search-foo on bugzilla is not what it used to be, and I don’t seem to find relevant bugs on this :-(.

This will help, add to your custom.css atm.

@media print {
    body, .txp-layout { display: block; } /* de-flexify those element for print media */
}

philwareham · 2016-10-09 08:16:29

The admin themes don’t have any specific target, such as media: screen, because I assumed people wouldn’t be printing the admin side. A fix for this would be for current CSS to be targeted at screen and then we write some basic print rules too.

Do you think this is worth doing? It is not much work to do.

colak · 2016-10-09 09:57:16

Hi Phil,

It might be my work methodology. For temporary memory prompts I print the back end on versioned pdfs which I then delete once I make the decision. Maybe I’m the only one doing it in which case no worries.

phiw13 · 2016-10-09 10:12:31

I don’t think it is worth spending much time on print-optimised rules for the TXP admin back-end. Ok, perhaps those couple of rules I flagged above to ensure that contents print in full with Firefox (only Firefox seems to have that issue, I think?).

Or do people would’ve a use case for printing e.g. their forms & templates for brainstorming in meetings? Or as a memo, taking some notes during development?

uli · 2016-10-09 13:14:41

My initial thought was removing all elements from display that aren’t within the main form. But then maybe exactly those elements outside are what shall be demonstrated or memorised.

One thing, though, that seems redundant is having the nav bar on each sheet/page.

phiw13 · 2016-10-09 13:20:47

uli wrote #302055:

One thing, though, that seems redundant is having the nav bar on each sheet/page.

.txp-header {position:fixed} does that for you, in Firefox (and maybe Edge, can’t remember atm).
But I agree it is redundant or even annoying in this case.

philwareham · 2016-10-09 14:14:28

Open an issue for this and I’ll write a few lines of CSS to accommodate printing. Cheers!

Textpattern CMS

Textpattern CMS support forum

#1 2016-10-08 17:16:41