I think I did everything correctly but e-mails from my campaign is not sending.
I’m trying using Mandrill. I configurate correctly this, because I tested sending test button and it works, so Mandrill is corresctly configurated.
I really like Mautic, but I’m having a little difficult to use it. Can you help me please? I want so much use this wonderful tool.
I think I did everything correctly but e-mails from my campaign is not sending.
I’m trying using Mandrill. I configurate correctly this, because I tested sending test button and it works, so Mandrill is corresctly configurated.
I really like Mautic, but I’m having a little difficult to use it. Can you help me please? I want so much use this wonderful tool.
Have you went through all these getting started steps?
https://www.mautic.org/getting-started/
Make sure cron jobs are configured correctly. Try to trigger the commands manually and see what it outputs.
@escopecz am also having the same challenge with the campaign. i have followed the steps on the getting started guide but emails cannot be sent to leads via campaigns
That means that cron jobs aren’t configured correctly. If you have a chance to see a cron job log or execute the mautic:campaign:trigger command and see the output, it will tell you what problem is there.
This is what i get from my email once i run the cron jobs…
" Mautic version 1.2.0 - app/prod
Usage:
command [options] [arguments]
Options:
–help (-h) Display this help message
–quiet (-q) Do not output any message
–verbose (-v|vv|vvv) Increase the verbosity of messages: 1 for normal output, 2 for more verbose output and 3 for debug
–version (-V) Display this application version
–ansi Force ANSI output
–no-ansi Disable ANSI output
–no-interaction (-n) Do not ask any interactive question
–shell (-s) Launch the shell.
–process-isolation Launch commands from shell as a separate process.
–env (-e) The Environment name. (default: “prod”)
–no-debug Switches off debug mode.
Available commands:
help Displays help for a command
list Lists commands
assets
assets:install Installs bundles web assets under a public web directory
bazinga
bazinga:oauth-server:clean Clean expired tokens
cache
cache:clear Clears the cache
cache:warmup Warms up an empty cache
config
config:debug Dumps the current configuration for an extension
config:dump-reference Dumps the default configuration for an extension
container
container:debug Displays current services for an application
debug
debug:swiftmailer Displays current mailers for an application
doctrine
doctrine:cache:clear-metadata Clears all metadata cache for an entity manager
doctrine:cache:clear-query Clears all query cache for an entity manager
doctrine:cache:clear-result Clears result cache for an entity manager
doctrine:database:create Creates the configured databases
doctrine:database:drop Drops the configured databases
doctrine:ensure-production-settings Verify that Doctrine is properly configured for a production environment.
doctrine:fixtures:load Load data fixtures to your database.
doctrine:generate:entities Generates entity classes and method stubs from your mapping information
doctrine:mapping:convert Convert mapping information between supported formats.
doctrine:mapping:import Imports mapping information from an existing database
doctrine:mapping:info
doctrine:migrations:diff Generate a migration by comparing your current database to your mapping information.
doctrine:migrations:execute Execute a single migration version up or down manually.
doctrine:migrations:generate Generate a blank migration class.
doctrine:migrations:latest Outputs the latest version number
doctrine:migrations:migrate Execute a migration to a specified version or the latest available version.
doctrine:migrations:status View the status of a set of migrations.
doctrine:migrations:version Manually add and delete migration versions from the version table.
doctrine:query:dql Executes arbitrary DQL directly from the command line.
doctrine:query:sql Executes arbitrary SQL directly from the command line.
doctrine:schema:create Executes (or dumps) the SQL needed to generate the database schema
doctrine:schema:drop Executes (or dumps) the SQL needed to drop the current database schema
doctrine:schema:update Executes (or dumps) the SQL needed to update the database schema to match the current mapping metadata.
doctrine:schema:validate Validate the mapping files.
fos
fos:oauth-server:clean Clean expired tokens
generate
generate:doctrine:entities Generates entity classes and method stubs from your mapping information
init
init:acl Mounts ACL tables in the database
mautic
mautic:assets:generate Combines and minifies asset files from each bundle into single production files
mautic:campaign:trigger Trigger timed events for published campaigns.
mautic:campaigns:rebuild Rebuild campaigns based on lead lists.
mautic:campaigns:trigger Trigger timed events for published campaigns.
mautic:campaigns:update Rebuild campaigns based on lead lists.
mautic:check:email Fetch and process monitored email.
mautic:check:mail Fetch and process monitored email.
mautic:email:process Processes SwiftMail’s mail queue
mautic:emails:process Processes SwiftMail’s mail queue
mautic:fetch:email Fetch and process monitored email.
mautic:fetch:mail Fetch and process monitored email.
mautic:install:data Installs Mautic with sample data
mautic:leadlists:rebuild Update leads in smart lists based on new lead data.
mautic:leadlists:update Update leads in smart lists based on new lead data.
mautic:lists:rebuild Update leads in smart lists based on new lead data.
mautic:lists:update Update leads in smart lists based on new lead data.
mautic:process:email Processes SwiftMail’s mail queue
mautic:process:emails Processes SwiftMail’s mail queue
mautic:rebuild:campaigns Rebuild campaigns based on lead lists.
mautic:rebuild:leadlists Update leads in smart lists based on new lead data.
mautic:rebuild:lists Update leads in smart lists based on new lead data.
mautic:send:email Processes SwiftMail’s mail queue
mautic:send:emails Processes SwiftMail’s mail queue
mautic:transifex:pull Fetches translations for Mautic from Transifex
mautic:transifex:push Pushes Mautic translation resources to Transifex
mautic:translation:createconfig Create config.php files for translations
mautic:translation:debug Displays translation messages informations
mautic:trigger:campaign Trigger timed events for published campaigns.
mautic:trigger:campaigns Trigger timed events for published campaigns.
mautic:update:apply Updates the Mautic application
mautic:update:campaigns Rebuild campaigns based on lead lists.
mautic:update:find Fetches updates for Mautic
mautic:update:leadlists Update leads in smart lists based on new lead data.
mautic:update:lists Update leads in smart lists based on new lead data.
mautic:webhooks:process Process queued webhook payloads
oneup
oneup:uploader:clear-chunks Clear chunks according to the max-age you defined in your configuration.
oneup:uploader:clear-orphans Clear orphaned uploads according to the max-age you defined in your configuration.
orm
orm:convert:mapping Convert mapping information between supported formats.
router
router:debug Displays current routes for an application
router:dump-apache Dumps all routes as Apache rewrite rules
router:match Helps debug routes by simulating a path info match
swiftmailer
swiftmailer:debug Displays current mailers for an application
swiftmailer:email:send Send simple email message
swiftmailer:spool:send Sends emails from the spool
translation
translation:debug Displays translation messages informations
translation:update Updates the translation file
yaml
yaml:lint Lints a file and outputs encountered errors
X-Powered-By: PHP/5.3.29
Set-Cookie: 92ed13a8b34d3da93ba3830a51e1b783=u4m1l403uepgil9fgiqbi78i03; path=/
Content-type: text/html"
Yep, that’s a list of available commands when you run
app/consoleBut you have to run specific commands from that list to make the automation work:
I think i have followed the steps here https://www.mautic.org/getting-started/
I have run the cron jons through my cpanel with an interval of once per minute.
Previously on running the cron jobs this is what i got via email which i think notified me of a problem on the folder path which i changed hence the above output
Status: 404 Not Found
X-Powered-By: PHP/5.3.29
Content-type: text/html
No input file specified.
I don’t understand from your answer if you managed to fix the problem or it is still remaining.
PHP 5.2.29 is not supported by Mautic. See requirements:
https://www.mautic.org/download/requirements/
From following link you can see that versions supported by PHP project are 5.5 and 5.6:
i have upgraded my php version to 5.5 but still facing the same problem
Check if the path to the Mautic commands is correct. Make a screen shot of the cron configuration if it doesn’t help.
can i give you access to it then you may help?
No, sorry. I’d prefer the screenshot.
Please find the screenshot for the cron jobs
I decided to use php mail and now i can trigger send email directly.
But the campaigns still cannot send emails
Sharing an image via Facebook. Never thought of that. Works though.
The screen shot has blank fields. I don’t need a blank form. I’d like to see what values have you inserted in it.
Well, do you mean this
*/5 * * * * php public_html/demo3/app/console mautic:leadlists:update --env=prod
*/5 * * * * php public_html/demo3/app/console mautic:campaigns:update --env=prod
*/5 * * * * php public_html/demo3/app/console mautic:campaigns:trigger --env=prod
*/5 * * * * php public_html/demo3/app/console mautic:email:process --env=prod
Yes, that’s better. I bet public_html is not a root directory. Take a look for example to Mautic’s configuration > Asset Settings. The real path should be a part of the asset directory path.
/home/websitem/public_html/demo3/app/console mautic:leadlists:update --env=prod
/home/websitem/public_html/demo3/app/console mautic:campaigns:update --env=prod
/home/websitem/public_html/demo3/app/console mautic:campaigns:trigger --env=prod
/home/websitem/public_html/demo3/app/console mautic:email:process --env=prod
i have used the above path…
Just wondering if i was supposed to include “php”
so that it could look like…
php /home/websitem/public_html/demo3/app/console mautic:email:process --env=prod
the php prefix should not be required since 1.2.0, but it won’t do any harm if you’ll leave it there. Those paths looks more like it.
If cron jobs are still not working, take a look if there is some log of executed cron jobs. Or maybe the log is sent to your email as you wrote earlier. Or, if you have SSH access to the server, you can take the command and execute it manually. If you don’t have SSH, use this script instead.
The point is to get output of those commands and see if they work as they should or if there is some PHP error preventing it. So, what’s the output?
yes the logs are sent to my email and i can see them already
Let me use the script then will let you know the output in 15 mins