J4.x:Assorted Issues - Revision history

Daneel at 22:37, 26 May 2024

2024-05-26T22:37:50Z

← Older revision		Revision as of 22:37, 26 May 2024
Line 82:		Line 82:
	</syntaxhighlight>		</syntaxhighlight>

	<translate><!--T:19--> If, by analyzing the table #__workflow_associations ~~before and~~ after ~~executing this~~ code, we find that the stage_id is 0 for all articles missing from the administration, then complete the process by executing the following query:</translate>		<translate><!--T:19--> If, by analyzing the table #__workflow_associations after the execution of the previous code, we find that the stage_id is 0 for all articles missing from the administration, then complete the process by executing the following query:</translate>

	<syntaxhighlight lang="sql">		<syntaxhighlight lang="sql">

Daneel at 22:21, 26 May 2024

2024-05-26T22:21:00Z

← Older revision		Revision as of 22:21, 26 May 2024
Line 89:		Line 89:

	<noinclude>		<noinclude>
			[[Category:Tips and tricks 4.x{{#translation:}}]]
			[[Category:Joomla!_4.x{{#translation:}}]]
	</noinclude>		</noinclude>

Daneel at 22:19, 26 May 2024

2024-05-26T22:19:57Z

← Older revision		Revision as of 22:19, 26 May 2024
Line 87:		Line 87:
	UPDATE `#__workflow_associations` SET `stage_id` = '1' WHERE `stage_id` = '0';		UPDATE `#__workflow_associations` SET `stage_id` = '1' WHERE `stage_id` = '0';
	</syntaxhighlight>		</syntaxhighlight>

			<noinclude>

			</noinclude>

Daneel at 22:18, 26 May 2024

2024-05-26T22:18:45Z

← Older revision		Revision as of 22:18, 26 May 2024
Line 1:		Line 1:
	<noinclude><languages /></noinclude>		<noinclude><languages /></noinclude>
	<translate>		<translate>
	== A Page Displays with No Styling == <!--T:1-->		== A Page Displays with No Styling == <!--T:1-->
	Possible cause: A gzip section in ''.htaccess'' is compressing the already-compressed CSS and JavaScript files.</translate>		Possible cause: A gzip section in ''.htaccess'' is compressing the already-compressed CSS and JavaScript files.</translate>

Daneel: Marked this version for translation

2024-05-26T22:18:20Z

Marked this version for translation

← Older revision		Revision as of 22:18, 26 May 2024
Line 1:		Line 1:
	<noinclude><languages /></noinclude>		<noinclude><languages /></noinclude>
	<translate>		<translate>
	== A Page Displays with No Styling ==		== A Page Displays with No Styling == <!--T:1-->
	Possible cause: A gzip section in ''.htaccess'' is compressing the already-compressed CSS and JavaScript files.</translate>		Possible cause: A gzip section in ''.htaccess'' is compressing the already-compressed CSS and JavaScript files.</translate>

	<translate>See this section of the ''.htaccess'' file:</translate>		<translate><!--T:2--> See this section of the ''.htaccess'' file:</translate>

	<syntaxhighlight>		<syntaxhighlight>
Line 19:		Line 19:
	</syntaxhighlight>		</syntaxhighlight>

	<translate>If present, comment out or remove.</translate>		<translate><!--T:3--> If present, comment out or remove.</translate>

	<translate>== The List of Site Modules is Empty ==		<translate>== The List of Site Modules is Empty == <!--T:4-->
	Possible cause: The MySQL sort buffer size may be too small.</translate>		Possible cause: The MySQL sort buffer size may be too small.</translate>

	<translate>Using phpMyAdmin, go to {{rarr\|Home,Variables,Sort buffer size}}.		<translate><!--T:5-->
			Using phpMyAdmin, go to {{rarr\|Home,Variables,Sort buffer size}}.

			<!--T:6-->
	It should be at least 256K and preferably 512K. On some shared hosting services, it may be set to 128K. Ask the hosting service to increase it.</translate>		It should be at least 256K and preferably 512K. On some shared hosting services, it may be set to 128K. Ask the hosting service to increase it.</translate>

	<translate>== Update Fails after Updating to 4.x ==		<translate>== Update Fails after Updating to 4.x == <!--T:7-->
	Cause: an essential change to the Update procedure affecting a small number of users.		Cause: an essential change to the Update procedure affecting a small number of users.

			<!--T:8-->
	Look in ''.htaccess'' for this line:</translate>		Look in ''.htaccess'' for this line:</translate>

Line 36:		Line 39:
	RewriteRule ^administrator/components/com_joomlaupdate/restore\.php$ - [L]</syntaxhighlight>		RewriteRule ^administrator/components/com_joomlaupdate/restore\.php$ - [L]</syntaxhighlight>

	<translate>Change it to:</translate>		<translate><!--T:9--> Change it to:</translate>

	<syntaxhighlight>		<syntaxhighlight>
	RewriteRule ^administrator\/components\/com_joomlaupdate\/extract\.php$ - [L]</syntaxhighlight>		RewriteRule ^administrator\/components\/com_joomlaupdate\/extract\.php$ - [L]</syntaxhighlight>

	<translate>For further information see:		<translate><!--T:10-->
			For further information see:

			<!--T:11-->
	[https://www.joomla.org/announcements/release-news/5850-changes-to-update-process-that-you-need-to-be-aware-of.html Changes to Update Process that you need to be aware of]</translate>		[https://www.joomla.org/announcements/release-news/5850-changes-to-update-process-that-you-need-to-be-aware-of.html Changes to Update Process that you need to be aware of]</translate>

	<translate>== Articles Visible in Database and Frontend but Not Visible in Backend ==		<translate>== Articles Visible in Database and Frontend but Not Visible in Backend == <!--T:12-->
	This occurs when articles are imported directly into the database, which worked fine in Joomla 3 but not in Joomla 4. One user's solution is as follows:</translate>		This occurs when articles are imported directly into the database, which worked fine in Joomla 3 but not in Joomla 4. One user's solution is as follows:</translate>

	<syntaxhighlight><translate>		<syntaxhighlight><translate>
			<!--T:13-->
	I imported articles directly in the database into the #__content table like I often did in Joomla 3.		I imported articles directly in the database into the #__content table like I often did in Joomla 3.
	However in Joomla 4 they were not visible.		However in Joomla 4 they were not visible.

			<!--T:14-->
	In Content > Categories, the category item counters counted the imported articles.		In Content > Categories, the category item counters counted the imported articles.
	But they were not visible in Content > Articles.		But they were not visible in Content > Articles.

			<!--T:15-->
	I solved it by creating the necessary references in the #__workflow_associations table for each imported article:		I solved it by creating the necessary references in the #__workflow_associations table for each imported article:
	item_id = article ID, stage_id = 1 and extension = com_content.article.</translate>		item_id = article ID, stage_id = 1 and extension = com_content.article.</translate>
	</syntaxhighlight>		</syntaxhighlight>

	<translate>With this from another user:		<translate><!--T:16-->
			With this from another user:

			<!--T:17-->
	This query should do it for you. Replace #__ with your own database prefix.		This query should do it for you. Replace #__ with your own database prefix.

			<!--T:18-->
	This query prevents duplicate items in the workflow associations table</translate>		This query prevents duplicate items in the workflow associations table</translate>

Line 71:		Line 82:
	</syntaxhighlight>		</syntaxhighlight>

	<translate>If, by analyzing the table #__workflow_associations before and after executing this code, we find that the stage_id is 0 for all articles missing from the administration, then complete the process by executing the following query:</translate>		<translate><!--T:19--> If, by analyzing the table #__workflow_associations before and after executing this code, we find that the stage_id is 0 for all articles missing from the administration, then complete the process by executing the following query:</translate>

	<syntaxhighlight lang="sql">		<syntaxhighlight lang="sql">
	UPDATE `#__workflow_associations` SET `stage_id` = '1' WHERE `stage_id` = '0';		UPDATE `#__workflow_associations` SET `stage_id` = '1' WHERE `stage_id` = '0';
	</syntaxhighlight>		</syntaxhighlight>

Daneel at 22:18, 26 May 2024

2024-05-26T22:18:06Z

← Older revision		Revision as of 22:18, 26 May 2024
Line 1:		Line 1:
			<noinclude><languages /></noinclude>
			<translate>
	== A Page Displays with No Styling ==		== A Page Displays with No Styling ==
	Possible cause: A gzip section in ''.htaccess'' is compressing the already-compressed CSS and JavaScript files.		Possible cause: A gzip section in ''.htaccess'' is compressing the already-compressed CSS and JavaScript files.</translate>

	See this section of the ''.htaccess'' file:		<translate>See this section of the ''.htaccess'' file:</translate>

	<syntaxhighlight>		<syntaxhighlight>
Line 17:		Line 19:
	</syntaxhighlight>		</syntaxhighlight>

	If present, comment out or remove.		<translate>If present, comment out or remove.</translate>

	== The List of Site Modules is Empty ==		<translate>== The List of Site Modules is Empty ==
	Possible cause: The MySQL sort buffer size may be too small.		Possible cause: The MySQL sort buffer size may be too small.</translate>

	Using phpMyAdmin, go to {{rarr\|Home,Variables,Sort buffer size}}.		<translate>Using phpMyAdmin, go to {{rarr\|Home,Variables,Sort buffer size}}.

	It should be at least 256K and preferably 512K. On some shared hosting services, it may be set to 128K. Ask the hosting service to increase it.		It should be at least 256K and preferably 512K. On some shared hosting services, it may be set to 128K. Ask the hosting service to increase it.</translate>

	== Update Fails after Updating to 4.x ==		<translate>== Update Fails after Updating to 4.x ==
	Cause: an essential change to the Update procedure affecting a small number of users.		Cause: an essential change to the Update procedure affecting a small number of users.

	Look in ''.htaccess'' for this line:		Look in ''.htaccess'' for this line:</translate>

	<syntaxhighlight>		<syntaxhighlight>
	RewriteRule ^administrator/components/com_joomlaupdate/restore\.php$ - [L]</syntaxhighlight>		RewriteRule ^administrator/components/com_joomlaupdate/restore\.php$ - [L]</syntaxhighlight>

	Change it to:		<translate>Change it to:</translate>

	<syntaxhighlight>		<syntaxhighlight>
	RewriteRule ^administrator\/components\/com_joomlaupdate\/extract\.php$ - [L]</syntaxhighlight>		RewriteRule ^administrator\/components\/com_joomlaupdate\/extract\.php$ - [L]</syntaxhighlight>

	For further information see:		<translate>For further information see:

	[https://www.joomla.org/announcements/release-news/5850-changes-to-update-process-that-you-need-to-be-aware-of.html Changes to Update Process that you need to be aware of]		[https://www.joomla.org/announcements/release-news/5850-changes-to-update-process-that-you-need-to-be-aware-of.html Changes to Update Process that you need to be aware of]</translate>

	== Articles Visible in Database and Frontend but Not Visible in Backend ==		<translate>== Articles Visible in Database and Frontend but Not Visible in Backend ==
	This occurs when articles are imported directly into the database, which worked fine in Joomla 3 but not in Joomla 4. One user's solution is as follows:		This occurs when articles are imported directly into the database, which worked fine in Joomla 3 but not in Joomla 4. One user's solution is as follows:</translate>

	<syntaxhighlight>		<syntaxhighlight><translate>
	I imported articles directly in the database into the #__content table like I often did in Joomla 3.		I imported articles directly in the database into the #__content table like I often did in Joomla 3.
	However in Joomla 4 they were not visible.		However in Joomla 4 they were not visible.
Line 54:		Line 56:

	I solved it by creating the necessary references in the #__workflow_associations table for each imported article:		I solved it by creating the necessary references in the #__workflow_associations table for each imported article:
	item_id = article ID, stage_id = 1 and extension = com_content.article.		item_id = article ID, stage_id = 1 and extension = com_content.article.</translate>
	</syntaxhighlight>		</syntaxhighlight>

	With this from another user:		<translate>With this from another user:

	This query should do it for you. Replace #__ with your own database prefix.		This query should do it for you. Replace #__ with your own database prefix.

	This query prevents duplicate items in the workflow associations table		This query prevents duplicate items in the workflow associations table</translate>

	<syntaxhighlight lang="sql">		<syntaxhighlight lang="sql">
Line 69:		Line 71:
	</syntaxhighlight>		</syntaxhighlight>

	If, by analyzing the table #__workflow_associations before and after executing this code, we find that the stage_id is 0 for all articles missing from the administration, then complete the process by executing the following query:		<translate>If, by analyzing the table #__workflow_associations before and after executing this code, we find that the stage_id is 0 for all articles missing from the administration, then complete the process by executing the following query:</translate>

	<syntaxhighlight lang="sql">		<syntaxhighlight lang="sql">
	UPDATE `#__workflow_associations` SET `stage_id` = '1' WHERE `stage_id` = '0';		UPDATE `#__workflow_associations` SET `stage_id` = '1' WHERE `stage_id` = '0';
	</syntaxhighlight>		</syntaxhighlight>

Daneel at 22:07, 26 May 2024

2024-05-26T22:07:54Z

← Older revision		Revision as of 22:07, 26 May 2024
Line 26:		Line 26:
	It should be at least 256K and preferably 512K. On some shared hosting services, it may be set to 128K. Ask the hosting service to increase it.		It should be at least 256K and preferably 512K. On some shared hosting services, it may be set to 128K. Ask the hosting service to increase it.

	== Update Fails after Updating to 4.~~0.4~~ ==		== Update Fails after Updating to 4.x ==
	Cause: an essential change to the Update procedure affecting a small number of users.		Cause: an essential change to the Update procedure affecting a small number of users.

Line 67:		Line 67:
	SELECT c.id as item_id, '1', 'com_content.article' FROM #__content AS c		SELECT c.id as item_id, '1', 'com_content.article' FROM #__content AS c
	WHERE NOT EXISTS (SELECT wa.item_id FROM #__workflow_associations AS wa WHERE wa.item_id = c.id);		WHERE NOT EXISTS (SELECT wa.item_id FROM #__workflow_associations AS wa WHERE wa.item_id = c.id);
			</syntaxhighlight>

			If, by analyzing the table #__workflow_associations before and after executing this code, we find that the stage_id is 0 for all articles missing from the administration, then complete the process by executing the following query:

			<syntaxhighlight lang="sql">
			UPDATE `#__workflow_associations` SET `stage_id` = '1' WHERE `stage_id` = '0';
	</syntaxhighlight>		</syntaxhighlight>

Daneel at 22:04, 26 May 2024

2024-05-26T22:04:15Z

← Older revision		Revision as of 22:04, 26 May 2024
Line 1:		Line 1:
	~~== Redirect Issue After Upgrade to 4.0.6 ==~~
	~~That is a bug! Line 243 of ''plugins/system/redirect/redirect.php'':~~

	~~<syntaxhighlight lang="php">~~
	~~$db->updateObject('#__redirect_links', $redirect, 'id');~~
	~~</syntaxhighlight>~~

	~~should be~~

	~~<syntaxhighlight lang="php">~~
	~~$this->db->updateObject('#__redirect_links', $redirect, 'id');~~
	~~</syntaxhighlight>~~

	== A Page Displays with No Styling ==		== A Page Displays with No Styling ==
	Possible cause: A gzip section in ''.htaccess'' is compressing the already-compressed CSS and JavaScript files.		Possible cause: A gzip section in ''.htaccess'' is compressing the already-compressed CSS and JavaScript files.

Alexandreelise: /* Articles Visible in Database and Frontend but Not Visible in Backend */

2022-11-09T16:29:48Z

Articles Visible in Database and Frontend but Not Visible in Backend

← Older revision		Revision as of 16:29, 9 November 2022
Line 73:		Line 73:

	This query should do it for you. Replace #__ with your own database prefix.		This query should do it for you. Replace #__ with your own database prefix.

			This query prevents duplicate items in the workflow associations table

	<syntaxhighlight lang="sql">		<syntaxhighlight lang="sql">
	~~INSERT INTO~~ #~~__workflow_associations~~		INSERT INTO #__workflow_associations (item_id, stage_id, extension)
	(item_id, ~~stage_id~~, ~~extension~~)		SELECT c.id as item_id, '1', 'com_content.article' FROM #__content AS c
	~~SELECT id as item_id~~, '1', 'com_content.article' ~~FROM~~ #~~__content~~;		WHERE NOT EXISTS (SELECT wa.item_id FROM #__workflow_associations AS wa WHERE wa.item_id = c.id);
	</syntaxhighlight>		</syntaxhighlight>

Cmb: Several markup changes.

2022-09-21T22:00:12Z

Several markup changes.

← Older revision		Revision as of 22:00, 21 September 2022
Line 1:		Line 1:
	== Redirect ~~issue after upgrade~~ to 4.0.6 ==		== Redirect Issue After Upgrade to 4.0.6 ==
			That is a bug! Line 243 of ''plugins/system/redirect/redirect.php'':
	That is a bug! Line 243 of plugins/system/redirect/redirect.php:

	<syntaxhighlight lang="php">		<syntaxhighlight lang="php">
Line 13:		Line 12:
	</syntaxhighlight>		</syntaxhighlight>

	== A ~~page displays~~ with ~~no styling~~ ==		== A Page Displays with No Styling ==
			Possible cause: A gzip section in ''.htaccess'' is compressing the already-compressed CSS and JavaScript files.

	~~Possible cause: A gzip section in .htaccess is compressing already compressed css and js files.~~		See this section of the ''.htaccess'' file:

	See this section of the .htaccess file:

	<syntaxhighlight>		<syntaxhighlight>
Line 31:		Line 29:
	</IfModule>		</IfModule>
	</syntaxhighlight>		</syntaxhighlight>

	If present, comment out or remove.		If present, comment out or remove.

	== The ~~list~~ of Site Modules is ~~empty~~ ==		== The List of Site Modules is Empty ==

	Possible cause: The MySQL sort buffer size may be too small.		Possible cause: The MySQL sort buffer size may be too small.

	Using phpMyAdmin, go to Home / Variables ~~/ sort~~ buffer size.		Using phpMyAdmin, go to {{rarr\|Home,Variables,Sort buffer size}}.

	It should be at least 256K and preferably 512K. On some shared hosting services it may be set to 128K. Ask the hosting service to increase it.		It should be at least 256K and preferably 512K. On some shared hosting services, it may be set to 128K. Ask the hosting service to increase it.

	== Update ~~fails~~ after ~~updating~~ to 4.0.4 ==		== Update Fails after Updating to 4.0.4 ==
			Cause: an essential change to the Update procedure affecting a small number of users.

	~~Cause: an essential change to the update procedure affecting a small number of users.~~		Look in ''.htaccess'' for this line:

	Look in .htaccess for this line:

	<syntaxhighlight>		<syntaxhighlight>
Line 57:		Line 54:
	For further information see:		For further information see:

	https://www.joomla.org/announcements/release-news/5850-changes-to-update-process-that-you-need-to-be-aware-of.html		[https://www.joomla.org/announcements/release-news/5850-changes-to-update-process-that-you-need-to-be-aware-of.html Changes to Update Process that you need to be aware of]

	~~== Articles visible in database and frontend but not visible in backend ==~~

			== Articles Visible in Database and Frontend but Not Visible in Backend ==
	This occurs when articles are imported directly into the database, which worked fine in Joomla 3 but not in Joomla 4. One user's solution is as follows:		This occurs when articles are imported directly into the database, which worked fine in Joomla 3 but not in Joomla 4. One user's solution is as follows:

Line 76:		Line 72:
	With this from another user:		With this from another user:

	This query should do it for you. Replace #_ with your own database prefix		This query should do it for you. Replace #__ with your own database prefix.

	<syntaxhighlight lang="sql">		<syntaxhighlight lang="sql">