Hi, a very useful and cool extension, thx!
I would have two feature requests/issues, if I may. At the moment it is only possible to post a job at one location. But if a company has multiple subsidiaries, and the same job is offered at multiple locations, one has to copy the job for each branch. It would be nice, if the editor could add several locations to the same job, and the json script would contain all jobLocation entries.

A second issue is the Joblist in the container. At the moment it is very difficult to find the job to be edited, as the joblist contains the datum of each job. It would be much more useful, if the editor could see the tite of each job instead.

Thanks, Ákos

Hi,
if I set "hiring_organization_logo_url" for a jobposting via "File" in the link assistant/pop up
the code in the generated JSON looks like:
logo":"t3://file?uid=74"

If I set it via "External URL", everything is fine. But that's maybe too complicated. (especially for an editor)
Is there any easier way I can set it correctly via selecting the image from fileadmin directly.

Thanks
Michael

If you leave this field empty then TYPO3 shows error:

Return value of Pegasus\GoogleForJobs\Domain\Model\Job::getValidThrough() must be an instance of DateTime, null returned.

So it has to be required, i think (TCA).

If the base_salary_enable button is disabled, the baseSalary attribute still gets added to the structured data. I believe this is a bug. This would be fixed in #23
As the baseSalary attribute is optional (at least for Google), I believe it should be possible not to add it.

Please remove the use Statement inside the ext_tables.php it can cause Problems, as a fix I would suggest to just use it directly:

\TYPO3\CMS\Core\Utility\ExtensionManagementUtility::addPiFlexFormValue

I am using your extension, thanks a lot!

Are you interested in changing the flexforms to switch the desired action directly instead of using redirects in the indexAction? I would then contribute the patch

Would you be interested in adding a direct_apply option to the structured data. This indicates if users can apply for a job directly on the website e.g. with a form. This would be added with #23

Since TYPO3 6.2 it is possible to categorize pages, content elements and
files (default setting) by using the internal generic categorization system.

Activating categorization by providing category flexform element for job
entries would be great as sys_category could be used to f.e. colorize
job-items according their category in List- and Detail-View.

(sys_category UID - only first category if more than one category is
selected per job entry - could be set f.e. as class on wrapping div)

On selecting the hiring Organization Logo the entry will be made on the backend, but the JSON script created on the front end does not contain it.

Hello together,
maybe you could help me with this, but I'm not really sure what you mean with the following items in your installation steps:

• "Create a plugin on a page"
  I guess you mean a plugin content element and select Google for Jobs? But on which page should I create the plugin? On every page where a job posting is located?
• "pid = "
  ??? Which news records do you mean here? Or which page id do I need here?
• "pageId = "
  Same here. Which page id do I need?

I'd really love to use your plugin, but as I'm at the beginning with typo3 I'd really appreciate your help with this!

Would you be interested in adding a title provider to the plugin? This way the job detail pages, could have a title corresponding to a job name e.g. JobName - MySite? If so I could create a pull request for pageTitle branch

Also would an opt-in or opt-out approach to this be preferred? You could always manually remove or add the page title provider like this in TypoScript:

config.pageTitleProviders {
    googleforjobs {
        provider = Pegasus\GoogleForJobs\PageTitle\GoogleForJobsPageTitleProvider
        before = altPageTitle,record,seo
    }
}

The Plugin Options are missing in version 2.0.0.
We will fix the problem as soon as possible!!!

First of all, my compliments for the great extension.

But I have the following problem (google_for_jobs 2.1, TYPO3 10.4.18, PHP 7.2).
On all pages with the list view plugin, parameters are automatically appended to the URLs.
They look like this
https://www.mydomain.de/karriere/stellenangebote?tx_googleforjobs_job[action]=listSelected&tx_googleforjobs_job[controller]=Job&cHash=105f0d079ba8b884872de3430df4d555
but should be:
https://www.mydomain.de/karriere/stellenangebote/

I added the following routeEnhancer to my config.yaml:

routeEnhancers:
  JobsPlugin:
    type: Extbase
    extension: GoogleForJobs
    plugin: Job
    routes:
      -
        routePath: '/{job-title}'
        _controller: 'Job::show'
        _arguments:
          job-title: job
    defaultController: 'Job::show' _arguments
    aspects:
      job-title:
        type: PersistedAliasMapper
        tableName: tx_googleforjobs_domain_model_job
        routeFieldName: path_segment

The links to the detail page are generated and working correctly.
Only the pages with the list views should not have anything appended to the URL.

What could be the reason for this?
Have I done something wrong?