Jump to content

MarkupSEO - The all-in-one SEO solution for ProcessWire.


Nico Knoll

Recommended Posts

11 minutes ago, adrian said:

Not sure - I fixed so many bugs I can't recall anymore 🙂 Maybe have a read through my Github commits - it might note this, not sure.

ha - great work on this - love the PW community! 😄 

I've tried dropping your branch of the module into one of the affected sites but it doesn't seem to have fixed it 😕. Bit puzzled, as I'm almost certain things were working fine on all these sites previously.

Link to comment
Share on other sites

  • 4 weeks later...

Should I uninstall the previous one first?

Quote

Compile Error: Cannot declare class MarkupSEO, because the name is already in use (line 12 of /domain.com /site/modules/MarkupSEO/MarkupSEO.module.php) 
This error message was shown because: site is in debug mode. ($config->debug = true; => /site/config.php). Error has been logged.

 

Link to comment
Share on other sites

Just now, Peter Knight said:

Should I uninstall the previous one first?

No need - that's just an error because PW doesn't like that I have added a .php extension to the module file when there is already a plain .module one installed. Just do a Modules > Refresh and you should be good.

Link to comment
Share on other sites

1 minute ago, adrian said:

No need - that's just an error because PW doesn't like that I have added a .php extension to the module file when there is already a plain .module one installed. Just do a Modules > Refresh and you should be good.

 

Thanks Adrian. 

That looks interesting. So essentially, I have more customised SEO options on a page level. Thanks for the work on this.

I don't have the image field available yet. I might try creating a few other images fields and generally good around and see if I can track down the issue.

Link to comment
Share on other sites

On 4/14/2019 at 6:06 PM, adrian said:

Actually @Peter Knight - you might try installing that version from scratch - I made several changes to fields and field types, so it might no longer be possible to simply upgrade from the old version.

I tracked down the culprit of the Image field not appearing in the Smart Image option of this module.

When an image field is set to Type=CroppableImages3, it is not recognised as an Images field.

Setting my Images field from CroppableImages3 back to plain old Image worked. Obviously, you then loose your CroppableImages3 function but this was just to prove a theory.

Not sure if this is something for you or @horst but just flagging here in case it's useful to anyone.

BTW, upgrading over the existing install seemed to work fine in general. It might be safer to install from scratch but that completely removes all my existing settings. I tried it on a development environment first. Phew!

 

Link to comment
Share on other sites

Hi, I am encoutering a strange issue, everything is on my local server, but I can't the customs value to print on the live stage.
I have tried erasing the whole site and installed a fresh export profile, I tried uninstalling and reinstalling the module, nothing works.
The data is in the db, so this either has to do with my server setup or a class import problem??

Anybody came across the same issue?
Thanks

Link to comment
Share on other sites

4 hours ago, iNoize said:

Its still renders the keywords Meta from The older versions. How can i hide the Keyword meta ? 

I you sure the keywords are being generated by this module? As you can see, I removed all references to them: https://github.com/adrianbj/MarkupSEO/commit/d6d65af93127b88f63d328d61c55fa2544133342

Are you definitely using that branch of my fork? I guess I should probably merge that branch into my master now.

Link to comment
Share on other sites

On 4/25/2019 at 4:00 PM, adrian said:

I you sure the keywords are being generated by this module? As you can see, I removed all references to them: https://github.com/adrianbj/MarkupSEO/commit/d6d65af93127b88f63d328d61c55fa2544133342

Are you definitely using that branch of my fork? I guess I should probably merge that branch into my master now.

I had the old one also installed and the keywords were in the templates. Now it works great thanks 

  • Like 1
Link to comment
Share on other sites

  • 1 month later...
  • 3 months later...
  • 1 year later...
12 hours ago, Ace864 said:

I don't really get how this app should work. Can someone help me, please? I recently started a new blog, and I am searching for a less costly way to promote it.

Hello, 
ok so what is the problem ? Ill try to explain it short. 

1. Install the Module 
2. Create a Field called  "seo"  with the type of "SeoMaestro"    (Screen 1)
3. Edit your Template e.G. basic to add Seo field to the template which you heve created    (Screen 2)
4. Put the code in your head from the site.    (Screen 3)

echo $page->seo->render();

 

So i hope you can understand:). The other settings you can setup in the seo  field under the "Details" tab 

 

1.png

2.png

3.png

  • Like 1
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Similar Content

    • By Sebi
      AppApiFile adds the /file endpoint to the AppApi routes definition. Makes it possible to query files via the api. 
      This module relies on the base module AppApi, which must be installed before AppApiFile can do its work.
      Features
      You can access all files that are uploaded at any ProcessWire page. Call api/file/route/in/pagetree?file=test.jpg to access a page via its route in the page tree. Alternatively you can call api/file/4242?file=test.jpg (e.g.,) to access a page by its id. The module will make sure that the page is accessible by the active user.
      The GET-param "file" defines the basename of the file which you want to get.
      The following GET-params (optional) can be used to manipulate an image:
      width height maxwidth maxheight cropX cropY Use GET-Param format=base64 to receive the file in base64 format.
    • By MarkE
      This fieldtype and inputfield bundle was built for storing measurement values within a field, rendering them in a variety of formats and converting them to other units or otherwise modifying them via the API.
      The API consists of a number of predefined functions, some of which include...
      render() for rendering the measurement object, valueAs() for converting the value to another unit value, convertTo() for converting the whole measurement object to different units, and add() and subtract() for for modifying the stored value by the value (converted as required) in another measurement. In the admin the inputfield includes a checkbox (which can be optionally disabled) for converting values on page save. For an example if a value was typed in as centimeters, the unit was changed to metres, and the page saved with this checkbox selected, said value would be automatically converted so that e.g. 170 cm becomes 1.7 m.

      A simple length field using Fieldtype Measurement and Inputfield Measurement.
      Combination units (e.g. feet and inches) are also supported.
      Please note that this module is 'proof of concept' at the moment - there are limited units available and quite a lot of code tidying to do. More units will be added shortly.
      See the GitHub at https://github.com/MetaTunes/FieldtypeMeasurement for full details and updates.
    • By tcnet
      File Manager for ProcessWire is a module to manager files and folders from the CMS backend. It supports creating, deleting, renaming, packing, unpacking, uploading, downloading and editing of files and folders. The integrated code editor ACE supports highlighting of all common programming languages.
      https://github.com/techcnet/ProcessFileManager

      Warning
      This module is probably the most powerful module. You might destroy your processwire installation if you don't exactly know what you doing. Be careful and use it at your own risk!
      ACE code editor
      This module uses ACE code editor available from: https://github.com/ajaxorg/ace

      Dragscroll
      This module uses the JavaScript dragscroll available from: http://github.com/asvd/dragscroll. Dragscroll adds the ability to drag the table horizontally with the mouse pointer.
      PHP File Manager
      This module uses a modified version of PHP File Manager available from: https://github.com/alexantr/filemanager
       
    • By tcnet
      This module implements the website live chat service from tawk.to. Actually the module doesn't have to do much. It just need to inserted a few lines of JavaScript just before the closing body tag </body> on each side. However, the module offers additional options to display the widget only on certain pages.
      Create an account
      Visit https://www.tawk.to and create an account. It's free! At some point you will reach a page where you can copy the required JavaScript-code.

      Open the module settings and paste the JavaScript-code into the field as shown below. Click "Submit" and that's all.

      Open the module settings
      The settings for this module are located int the menu Modules=>Configure=>LiveChatTawkTo.

       
    • By tcnet
      Session Viewer is a module for ProcessWire to list session files and display session data. This module is helpful to display the session data of a specific session or to kick out a logged in user by simply delete his session file. After installation the module is available in the Setup menu.

      The following conditions must be met for the module to work properly:
      Session files
      Session data must be stored in session files, which is the default way in ProcessWire. Sessions stored in the database are not supported by this module. The path to the directory where the session files are stored must be declared in the ProcessWire configuration which is by default: site/assets/sessions.
      Serialize handler
      In order to transform session data easier back to a PHP array, the session data is stored serialized. PHP offers a way to declare a custom serialize handler. This module supports only the default serialize handlers: php, php_binary and php_serialize. WDDX was dropped in PHP 7.4.0 and is therefore not supported by this module as well as any other custom serialize handler. Which serialize handler is actually used you can find out in the module configuration which is available under Modules=>Configure=>SessionViewer.

      Session data
      The session data can be displayed in two different ways. PHP's default output for arrays print_r() or by default for this module nice_r() offered on github: https://github.com/uuf6429/nice_r. There is a setting in the module configuration if someone prefers print_r(). Apart from the better handling and overview of the folded session data the output of nice_r() looks indeed nicer.

      Links
      ProcessWire module directory
      github.com
×
×
  • Create New...