TypeError: $(...).disableSubmit is not a function

[arcadius <arcadius@…>]

Trac pages (f.e. timeline) are loaded with javascript error. Firefox gives:

TypeError: $(...).disableSubmit is not a function 1 38:66:9
	<anonymous> https://../ticket/38:66:9
	f.Callbacks/o https://../chrome/common/js/jquery.js:2:14728
	f.Callbacks/p.fireWith https://../chrome/common/js/jquery.js:2:15502
	f</<.ready https://../chrome/common/js/jquery.js:2:9592
	f</B https://../chrome/common/js/jquery.js:2:14288

Error occurs in statement $(".trac-disable").disableSubmit(".trac-disable-determinant");.

[Jun Omae]

What browser are you using?

[Jun Omae]

Replying to Jun Omae:

What browser are you using?

Sorry. I noticed you're using Firefox.

[Jun Omae]

No such errors in demo-1.2/timeline. Please confirm whether the same error occurs after disabling all plugins.

[arcadius <arcadius@…>]

Browser: Mozilla 51.0.1 (32-bit).

I deleted all records from [components] section in trac.ini - error remains.

My Trac enviroment & file ticket_notify_email.txt, changed by me according to this tip, can be downloaded ​here (base_url & database connection string removed).

Maybe, this error is the reason why auto-preview feature stopped to work on my server after upgrading to 1.2 .

[Jun Omae]

Clear browser cache and confirm trac.js in your site is the same as tags/trac-1.2/trac/htdocs/js/trac.js​.

[arcadius <arcadius@…>]

Yes, files were different. When I replaced <enviroment>/htdocs/common/js/trac.js with actual file, JS error disappeared, auto-preview started to work again. Thank you!

Maybe I did something wrong during upgrading FreeBSD port trac-1.0.13 to trac-1.2

[Jun Omae]

Thanks for the feedback. That's an InstallationIssue. Closing as cantfix.

[Ryan J Ollos]

Replying to arcadius <arcadius@…>:

Yes, files were different. When I replaced <enviroment>/htdocs/common/js/trac.js with actual file, JS error disappeared, auto-preview started to work again. Thank you!

Maybe I did something wrong during upgrading FreeBSD port trac-1.0.13 to trac-1.2

You may have skipped TracUpgrade#a5.Refreshstaticresources. If your webserver is configured to server static resources (TracInstall#MappingStaticResources), then you are probably now serving all of the old js and css files with the exception of trac.js which you just manually replaced. If you need more help sorting this out please ask on the MailingList.

[arcadius <arcadius@…>]

Replying to arcadius <arcadius@…>:

… You may have skipped TracUpgrade#a5.Refreshstaticresources. …

You are right. Now I updated static resources with trac-admin /path/to/env deploy /deploy/path. Everything is fine except one non-critical thing.

Inside /deploy/path/htdocs were created 2 directories: common and site, it's OK. But inside site were also created these 2 directories: site/common and site/site, with the same contents as parent directories, and so on. The most deep directory is site/site/site/site, which contains only common and no site.

[anonymous]

Inside /deploy/path/htdocs were created 2 directories: common and site, it's OK. But inside site were also created these 2 directories: site/common and site/site, with the same contents as parent directories, and so on. The most deep directory is site/site/site/site, which contains only common and no site.

Sounds like #10316.

[Ryan J Ollos]

Replying to arcadius <arcadius@…>:

Inside /deploy/path/htdocs were created 2 directories: common and site, it's OK. But inside site were also created these 2 directories: site/common and site/site, with the same contents as parent directories, and so on. The most deep directory is site/site/site/site, which contains only common and no site.

I suggest deploying with a directory structure like:

• /path/to/env
• /path/to/deploy

rather than deploying into /path/to/env. The files in env/htdocs will be extracted during the deploy step, so make sure to delete the files you previously deployed into that directory. You'll need to change your web server configuration after moving /path/to/deploy.

[anonymous]

Replying to Ryan J Ollos:

I deployed into empty directory and got there «recursive» odd structure described above.

[Ryan J Ollos]

Replying to anonymous:

Replying to Ryan J Ollos:

I deployed into empty directory and got there «recursive» odd structure described above.

Was the empty directory outside of $env? Please list the contents of your $env/htdocs. Are you using a shared htdocs directory?

[arcadius <arcadius@…>]

Replying to Ryan J Ollos:

Was the empty directory outside of $env? Please list the contents of your $env/htdocs. Are you using a shared htdocs directory?

What is «$env»? Both directories (Trac enviroment and deployment output) don't intersect. You can download them ​here. There's htdocs_dir in [inherit] section, but it's set to empty value.

[Ryan J Ollos]

Replying to arcadius <arcadius@…>:

What is «$env»? Both directories (Trac enviroment and deployment output) don't intersect. You can download them ​here. There's htdocs_dir in [inherit] section, but it's set to empty value.

$env is that path to your environment directory. I looked at your zip file. You've deleted env/htdocs so deploy/htdocs/site should not exist, however it contains the recursive copies. Please delete the deploy directory, and then run trac-admin env deploy deploy while you current directory is the parent of env and deploy.

[arcadius <arcadius@…>]

Yes, this zip is out-of-date, now no recursive folders are created. Recursion occurs only if there's $env/htdocs (see zip in comment:5).

[Ryan J Ollos]

Okay, I misunderstood and thought you were still having troubles. For sanity, you may want to restore an empty htdocs directory below your environment directory, since it's useful and expected to be present in case you do any interface customization.