spf_js - JavaScript management - create, edit, delete, export to file

spiffin · 2012-11-03 00:32:38

Version 0.5 released for Textpattern >= 4.5.1

MarcoK · 2012-11-06 17:58:57

Hi Simon,

I have a problem with new version: 0.5
I have tried instal into a new TXP installation and the plugin not create the prefs field.
So, it show the default script but not save or alter it and I can’t create a new script.

I solved installing version 0.4 and then update to 0.5.

spiffin · 2012-11-06 18:16:37

MarcoK wrote:

I have tried instal into a new TXP installation and the plugin not create the prefs field.

Hi Marco

Thanks for spotting that .. a new version will be out very soon.

EDIT: fixed version (v0.51) out now.

Simon

Last edited by spiffin (2012-11-07 20:42:44)

Derekstaff · 2014-12-01 22:09:02

I’m having a difficult time getting spf_js to work on my site. As I’ve mentioned in other threads, this is my first time working with more than bare html and css sites, so forgive me if I’m being a bit dense, missing something obvious.

I’m currently developing on my server in a subdirectory (www.mydomainname.com/test) while I work on the site upgrade. The Textpattern installation/directory is in the “test” subdirectory. When the Github page for the plugin states:

“Create a directory for the static JavaScript files in the root of your textpattern installation. You should make sure that PHP is able to write to that directory.”

That means I would put the “js” directory in the “test” directory, correct? Because, for the purposes of developing this upgrade, “test” is the root, right? Or do I put the “js” directory in the “textpattern” directory within the “test” directory?

When the Github page instructions say:

“Visit the Advanced Preferences (Admin > Preferences > Advanced) and make sure the “JavaScript directory” preference contains the directory you created in step 1 (by default ‘js’). “

That means I would put “www.mydomainname.com/test/js” as the path in the Javascript entry under Advanced Preferences, correct?

Thanks for helping me understand.

spiffin · 2014-12-01 22:39:39

Hello

1. Put the ‘js’ directory in your root directory – in your case inside the ‘test’ directory.

2. Under Advanced Prefs just enter ‘js’ (it’s in relation to your root directory).

Simon

Derekstaff · 2014-12-01 23:22:30

Thanks. Ok, that’s what I thought. I’d put the “js” directory inside of “test”, and had left the “javascript” path in the advanced setting at it’s default “js”. I made sure the plugin was installed and activated. But it doesn’t seem to be working.

I’ve installed and activated the spf_js plugin. I created a form, “js_link” which simply outputs <txp:spf_js />, and then included the tag <txp:output_form form="js_link"> on each page, so that I could quickly change the javascript link if need be.

To see if the javascript was functioning, I included this basic function to the default javascript file.
function popup() { alert("Hello World") }

And added this to my default txp page.

<input type="button" onclick="popup()" value="Click Me!">

When I checked the site in the browser, the “Click Me!” button was of course created, but I’m not getting any popup. I can’t seem to figure out what the problem is.

spiffin · 2014-12-01 23:54:02

You don’t need to create a form etc.

Once you’ve added your javascript to the default javascript just add <txp:spf_js /> to the relevant page template.

If you’re still having trouble, can you go to Admin > Diagnostics and tell me what is says for Document root and $path_to_site?

Last edited by spiffin (2014-12-02 00:16:44)

Derekstaff · 2014-12-02 21:02:03

I understand that I don’t need to create a form for the link, but was worried that I wouldn’t get the plugin to work properly, and Figured it would be easier to change a form than to change the link on several different pages if I end up trying to deal with the javascript manually.

According to diagnostics:

Document root: /home/43/94/8309443/web
$path_to_site: /home/43/94/8309443/web/test

Thanks for trying to help me figure this out.

spiffin · 2014-12-02 21:10:57

Hmm .. all looks fine to me.

I set up a quick local install of Textpattern in a sub-directory to test and it works fine.

If you look at the page source can you see the javascript?

Derekstaff · 2014-12-02 21:29:00

Just on a lark, I got rid of the form, and put the <txp:spf_js /> directly on the page template. The basic javascript now runs. Go figure.

I appreciate the help. I’ll start putting the more complex javascript in and see if it all continues to work.

Thanks for looking into this with me.

spiffin · 2014-12-02 21:56:25

Your form tag wasn’t closed:

<txp:output_form form=“js_link”>

.. instead of:

<txp:output_form form=“js_link” />

Derekstaff · 2014-12-02 22:15:50

Whoops! thanks for the catch.

Textpattern CMS

Textpattern CMS support forum

#37 2012-11-03 00:32:38

Re: spf_js - JavaScript management - create, edit, delete, export to file

#38 2012-11-06 17:58:57

Re: spf_js - JavaScript management - create, edit, delete, export to file

#39 2012-11-06 18:16:37

Re: spf_js - JavaScript management - create, edit, delete, export to file

#40 2014-12-01 22:09:02

Re: spf_js - JavaScript management - create, edit, delete, export to file

#41 2014-12-01 22:39:39

Re: spf_js - JavaScript management - create, edit, delete, export to file

#42 2014-12-01 23:22:30

Re: spf_js - JavaScript management - create, edit, delete, export to file

#43 2014-12-01 23:54:02

Re: spf_js - JavaScript management - create, edit, delete, export to file

#44 2014-12-02 21:02:03

Re: spf_js - JavaScript management - create, edit, delete, export to file

#45 2014-12-02 21:10:57

Re: spf_js - JavaScript management - create, edit, delete, export to file

#46 2014-12-02 21:29:00

Re: spf_js - JavaScript management - create, edit, delete, export to file

#47 2014-12-02 21:56:25

Re: spf_js - JavaScript management - create, edit, delete, export to file

#48 2014-12-02 22:15:50

Re: spf_js - JavaScript management - create, edit, delete, export to file

Board footer