By Paul Murray on Friday, 02 September 2016
Posted in MetaMan
Likes 0
Views 1.1K
Votes 0
Hi StacksIdeas Team

When I go here:
http://www.finalbug.net/

I make sure that I can access the front end as a super admin.
(Disabled this feature in Akeeba Admin Tools for the moment)

Please see this post for more details:

http://stackideas.com/forums/firing-up-metaman

Any changes that I save using the first “link” button/tool do not get save.

To be precise:
MetaMan goes through the motions of saving.
As soon as I click on the link button after editing and saving
The changes are gone!

I did an idiot check to see if I could edit the article on this page from the front end which I could do.
So I can confirm that I can at least edit stuff that shows up on a normal web page at the front end!

Please advise

thanks

Paul
hey there,

I already help you updated to 1.0.7 latest version, it should work fine now, can you give it a check?
·
Friday, 02 September 2016 01:54
·
0 Likes
·
0 Votes
·
0 Comments
·
hey Arlex

Wow that was fast
This is better. But...
This is the current state of play at my end!

- I login as Super Admin
- Go to the home page
- Click the 1st MetaMan button
- Enter for eg a new Keyword
- Press Save
- Close the Meta Man Editor
- Open it again and see that the change is not saved!!!

***************************************************************

- Log Out
- I login again as Super Admin
- See that the change has indeed been saved.

***************************************************************

Could you kindly check if you are experiencing the same?

thanks in advance

Paul
·
Friday, 02 September 2016 02:37
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Paul,

You're welcome

The reason why it didn't show the correct value when you update the meta value close it and open again without refresh the page is because the jQuery only can find the meta value within the page.

The webpage haven't update the meta value yet when you save the custom meta at the same time, but it actually already stored the meta value in database, when you refresh the page, it will show correctly.

We will see if that is possible to get the better solution in the future release version so when you click close the tab and open, it will always get updated the latest meta value.
·
Friday, 02 September 2016 11:00
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Arlex

I entered the following Keywords in the Keywords section of MetaMan for my home page.

Apple FCPX Trainer, Paul David Murray, Berlin FCPX Training, Learning FCPX, Free FCPX Tutorials, Final Cut Pro X Certified Apple Trainer, Free FCPX Resources, FCXP for beginners, Beginners Guide to FCPX, FCPX Editing, FCPX Editor Berlin Germany

Pressed save, refreshed and opened MetaMan again.

I see them they are there.

Great. So far so good.

If I use this plugin here in Chrome:

https://chrome.google.com/webstore/detail/meta-seo-inspector/ibkclpciafdglkjkcibmohobjkcfkaef?hl=en

And go to my home page and activate this plugin in Chrome.

I see the following keyword: “Bruce Speaks”

No sign of the Keywords i entered above…

My questions:

a) Does it take time for Google to pick up on these new Keywords?
b) Could I use this Plugin to double check that my keywords are kicking in?
c) Something else?

I just want to double check this before I proceed with 100s of pages ;-)

thanks

Paul
·
Friday, 02 September 2016 15:06
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Paul,

I've checked in your homepage in Chrome browser, it seems like that meta SEO inspector did show your latest keyword what you set from the MetaMan tag, you can refer on my attached screenshot below.

It actually no need to wait for Google pick up these keyword, because it should show immediately.
·
Friday, 02 September 2016 16:26
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Arlex

OK this is good to know.
Maybe I had some Cache issues
I am going through my top level pages and will keep an eye on this.

but am way less paranoid now

thanks

Paul

ps: just thinking aloud here, I had Meta Man open in Opera & the SEO Chrome plugin open in emmmm Chrome. For the simple reason that both were displaying on the right hand side and I could not see them both in the same browser at the same time.

Maybe it would be a good idea to be able to say where MetaMan shows up? eg Left, Right, Top, Bottom?

One of the nice things about the Chrome plugin is it tells me if I have the right number of characters etc...
·
Friday, 02 September 2016 16:43
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi there,


Maybe it would be a good idea to be able to say where MetaMan shows up? eg Left, Right, Top, Bottom?

One of the nice things about the Chrome plugin is it tells me if I have the right number of characters etc...

We will see if that it is possible to get have this feature in future release version. Thanks for the input Paul
·
Friday, 02 September 2016 19:39
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Stackideas

I hate to say this I believe that there is still something weird going on here.
Please check out the screen shots for the home page.

MetaMan shows me how I entered stuff.
Google SEO plugin shows me how things were before I made the changes.
A google search for "final bug" shows me the way the text used to be.

I am seeing inconsistencies across multiple pages!

please advise

Paul
·
Sunday, 04 September 2016 22:55
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Paul,

The reason that the meta isn't updating is because the MetaMan plugin was set with restrictive access, http://take.ms/3WPdo

You need to leave this to public but the tool will not appear for the user of course as we have our own ACL checks Now that I have set the plugin to public, can you try this again?


P/S: Since 1.0.7, you can already configure the acl in the plugin settings, http://take.ms/JU3cu
·
Sunday, 04 September 2016 23:47
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Mark

I can confirm that this works now.

thank you very much

Paul
·
Tuesday, 06 September 2016 22:39
·
0 Likes
·
0 Votes
·
0 Comments
·
Thanks for updating me on this Paul, am glad that your issues are resolved now
·
Tuesday, 06 September 2016 22:48
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post