Skip to content
This repository has been archived by the owner on May 19, 2020. It is now read-only.

Meta data page issues #222

Closed
shoostar opened this issue Feb 28, 2013 · 12 comments
Closed

Meta data page issues #222

shoostar opened this issue Feb 28, 2013 · 12 comments

Comments

@shoostar
Copy link

I noticed two things on the "Meta Data" page: for one, the Twitter handle section has mysteriously been removed (unless that was done with purpose), and I also noticed that (besides going through the database manually) there's no way to remove custom meta fields after you create them for this page.

@daviddarnes
Copy link
Member

You can add the twitter handle stuff by nicking it from Default I think, check the functions file.

@shoostar
Copy link
Author

That's what I ended up doing. Also, I noticed that if you create a custom field in the "Extend" section, trying to edit it gives this error:

Uncaught Exception

Class 'Str' not found
Origin

anchor\views\extend\fields\edit.php on line 4
Trace

#0 [internal function]: System\Error::shutdown()
#1 {main}

@daviddarnes
Copy link
Member

I think the twitter option has been taken out because its not essential to the CMS.

In regards to that error, got no idea. dev or master copy?

@shoostar
Copy link
Author

Dev. I added a field that gets used in a "tweet this" button for articles. It works perfectly fine, just can't edit the field parameters.

As for the actual Twitter account meta field, that's totally understandable. I just hard-coded the link into my HTML.

@daviddarnes
Copy link
Member

You're probably better off using the master as there's probably some new features that are conflicting with it.

@shoostar
Copy link
Author

I wouldn't be surprised if that's the case. Regardless, everything on the front-end of it all works just fine, so I'm not really too concerned. As a matter of fact, I'll probably keep on using the dev branch just to help point out bugs and whatnot.

@saltandvinegarcrisps
Copy link
Member

Yea, this is being replace with global custom fields, so you can add not only your twitter account but others like your google analytics account etc. Just do a git pull on your dev copy, when I commit new features I try to make sure it doesn't break the dev branch, but sometimes thats not always the case.

@daviddarnes
Copy link
Member

Not to worry Kieron, the work you've done so far is fantastic! And I like the sound of the Google analytics code field too.

@shoostar
Copy link
Author

shoostar commented Mar 4, 2013

I agree with David on that, you've all done some amazing work with this CMS, and I'm glad I chose to keep using this instead of any other CMS to power my blog. Speaking of Google Analytics, I've been thinking about going ahead and creating something similar for GoSquared as well, seeing as how I use that instead of Google.

@daviddarnes
Copy link
Member

@shoostar They are both implemented in a similar manner, just some javascript at the bottom of the page before the end of the body. Just needs a large metabox for it in the Metadata section I guess.

@jordankoschei
Copy link

A basic "Footer Analytics Code" textarea would cover all our bases.

@daviddarnes
Copy link
Member

Global custom fields has been added to the dev version, sorted.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants